Maven 2.x and 3.x Site Plugin

mechanism for local preview of a multiproject site tree

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: site:run
  • Labels:
    None
  • Number of attachments :
    0

Description

currently difficult as they are in target/site/*, where the links rely on ./

Issue Links

This issue is superceded by:
MSITE-562 site:run does not work with multi-module site Major Open

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Brett Porter added a comment -

site:stage does this, but it would be good to make site:run capable of it.

It might be a good idea to have site:stage run the site lifecycle instead, and put it all into the target directory of the root project

Show
Brett Porter added a comment - site:stage does this, but it would be good to make site:run capable of it. It might be a good idea to have site:stage run the site lifecycle instead, and put it all into the target directory of the root project
Hide
Permalink
John Allen added a comment -

stage was supposed to be a peer of deploy, ie a 'deploy to local directory' function - then we added the 'deploy to remote directory' so we could properly stage our sites. But anyways my point is that consistency is best and as deploy doesnt generate stuff then neither should stage. Plus I absolutely hate it when plugins get too clever and start forking off lifecycles as this 'atomic' build behaviour is hardly ever what you want in a complex build.

Show
John Allen added a comment - stage was supposed to be a peer of deploy, ie a 'deploy to local directory' function - then we added the 'deploy to remote directory' so we could properly stage our sites. But anyways my point is that consistency is best and as deploy doesnt generate stuff then neither should stage. Plus I absolutely hate it when plugins get too clever and start forking off lifecycles as this 'atomic' build behaviour is hardly ever what you want in a complex build.
Hide
Permalink
SebbASF added a comment -

I agree - site:stage should just amalgamate the target/site directories in the correct relative locations, not try and build them first.

Show
SebbASF added a comment - I agree - site:stage should just amalgamate the target/site directories in the correct relative locations, not try and build them first.
Hide
Permalink
Lukas Theussl added a comment -

site:stage now (v. 2.3-snap) behaves as noted above, see MSITE-533. However, site:run cannot be used to preview the multi-module build tree, it only works on the current site.

Show
Lukas Theussl added a comment - site:stage now (v. 2.3-snap) behaves as noted above, see MSITE-533. However, site:run cannot be used to preview the multi-module build tree, it only works on the current site.

People

Vote (6)
Watch (4)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.