You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2005/12/20 07:13:44 UTC
[jira] Moved: (MSITE-44) make site reactor aware
[ http://jira.codehaus.org/browse/MSITE-44?page=all ]
Jason van Zyl moved MNG-384 to MSITE-44:
----------------------------------------
Version: (was: 2.0-alpha-2)
Fix Version: (was: 2.1)
type: Bug (was: Improvement)
Component: (was: maven-site-plugin)
Workflow: jira (was: Maven)
Key: MSITE-44 (was: MNG-384)
Project: Maven 2.x Site Plugin (was: Maven 2)
> make site reactor aware
> -----------------------
>
> Key: MSITE-44
> URL: http://jira.codehaus.org/browse/MSITE-44
> Project: Maven 2.x Site Plugin
> Type: Bug
> Reporter: Brett Porter
> Priority: Blocker
>
>
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org