[ http://jira.codehaus.org/browse/MNG-661?page=comments#action_52647 ]
John Allen commented on MNG-661: -------------------------------- Hi Vincent, Yeah i think this is a more approrpiate approach, especially as its only intended for testing. So the key to the the simulate mode is that all projects referenced by the reactor env. will be expected to share a common URL root and this root will be set by a plugin config rather than try and use the main POM. This would be great and would solve another problem i have with my CI based builds - In CI builds i still wnat to build the sites to allow project teams to access the latest SNAPSHOT javadocs, review code coverage etc without me having to deploy the site to the 'offical' location (a task I associate with a project deployment, not just CI builds) I think we should also support the deployment of this 'simulated' site to a remote site which leads me to thinking that all this link URL business is pretty much dependent on where we're intending to deploy things to (staged or deployed/published location) so should we make the settings of these URLs something that the deploy operation does as a preparatory action? site:site - generate site for deployment but create placeholders for links site:stage - set parent and module links to file:// URLs based upon the project's distributionManagement.site details (i.e. exactly as you proposed) and then deploy the site to the location defined by the Mojo config (this supports us scp'ing the staged site to a remote host and implicitly supports the stagingDirectory you proposed) site:deploy - set parent and module links to URLs defined the project's real URL details (i.e. as my patch currently assumes) and then deploy the sites as defined by their distributionManagement settings (which must be related to their project.URLs otherwise the POM writer has screwed up:) ) We're definately getting their :- WDYT ... ps. in regards to naming, staging is a common term for review/testing of a web site. Do we want to just call this site:stage rather than simulate? I know to us its simulating the real site deployment but in terms of business process the user is staging it for testing or local review. Not gonna get religous over about it though :) > In parent site, automatically create link to modules sites and vice-versa > ------------------------------------------------------------------------- > > Key: MNG-661 > URL: http://jira.codehaus.org/browse/MNG-661 > Project: Maven 2 > Type: Improvement > Components: maven-site-plugin > Versions: 2.0-alpha-3 > Reporter: Yann Le Du > Assignee: Vincent Siveton > Priority: Minor > Fix For: 2.0.1 > Attachments: SiteMojoPatch.txt, SiteMojoPatch.txt, SiteMojoPatch.txt > > > Say we have the following project structure : > A > +-- B > +-- C > +-- D > It would be nice to have the following links in the left menu of the > generated sites : > A : > Modules : B, D > B : > Parent : A > Modules : C > C : > Parent : B > D : > Parent : A -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
