[ http://jira.codehaus.org/browse/MNG-384?page=comments#action_47338 ]
Brett Porter commented on MNG-384: ---------------------------------- m1 didn't have any site aggregation... the multiproject links are already in place - this is to make it smarter. The dashboard is a different case. The statement about Maven is really meant to reflect on the feature set of the core, rather than availability of plugins. About 75% of them are at the same level as m1, but dashboard is not one of them. > make site reactor aware > ----------------------- > > Key: MNG-384 > URL: http://jira.codehaus.org/browse/MNG-384 > Project: Maven 2 > Type: Improvement > Components: maven-site-plugin > Versions: 2.0-alpha-2 > Reporter: Brett Porter > Priority: Blocker > Fix For: 2.1 > > > there are a few things I'd like to do to make the sites more workable: > - it's good they can still build independantly > - however, if built from the parent, it would be good to go into aggregation > mode and pull in those separately built sites, do any dashboards and deploy > together > - some reports would aggregate themselves, as well as participate in the > dashboards (eg javadoc) > - I'd like the navigation to behave hierachically (sections of the parent > navigation marked as inherited remain on the child sites) > - this means that when building from independant projects they'd need to be > able to locate the parent site descriptor. This could be tricky without a USD > - should it fail if it is not a USD, or should the site descriptor be > published/referenced externally somehow? -- 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]
