You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/05/12 15:22:21 UTC
[jira] Created: (MNG-384) make site reactor aware
make site reactor aware
-----------------------
Key: MNG-384
URL: http://jira.codehaus.org/browse/MNG-384
Project: m2
Type: Improvement
Components: maven-plugins
Versions: 2.0-alpha-2
Reporter: Brett Porter
Fix For: 2.0-beta-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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-384) make site reactor aware
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-384?page=all ]
John Casey updated MNG-384:
---------------------------
Assign To: (was: John Casey)
Fix Version: (was: 2.0-beta-3)
2.1
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-384) make site reactor aware
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-384?page=all ]
Brett Porter updated MNG-384:
-----------------------------
Priority: Blocker (was: Major)
> make site reactor aware
> -----------------------
>
> Key: MNG-384
> URL: http://jira.codehaus.org/browse/MNG-384
> Project: Maven 2
> Type: Improvement
> Components: maven-plugins
> Versions: 2.0-alpha-2
> Reporter: Brett Porter
> Priority: Blocker
> Fix For: 2.0-beta-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 dashboarFrom dev-return-41986-apmail-maven-dev-archive=maven.apache.org@maven.apache.org Wed Jul 20 07:11:06 2005
Return-Path: <de...@maven.apache.org>
Delivered-To: apmail-maven-dev-archive@www.apache.org
Received: (qmail 31401 invoked from network); 20 Jul 2005 07:11:04 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
by minotaur.apache.org with SMTP; 20 Jul 2005 07:11:04 -0000
Received: (qmail 93083 invoked by uid 500); 20 Jul 2005 07:10:40 -0000
Delivered-To: apmail-maven-dev-archive@maven.apache.org
Received: (qmail 91413 invoked by uid 500); 20 Jul 2005 07:10:24 -0000
Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <ma...@maven.apache.org>
List-Help: <ma...@maven.apache.org>
List-Post: <ma...@maven.apache.org>
List-Id: "Maven Developers List" <dev.maven.apache.org>
Reply-To: "Maven Developers List" <de...@maven.apache.org>
Delivered-To: mailing listds 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
dev@maven.apache.org
Received: (qmail 90299 invoked by uid 99); 20 Jul 2005 07:10:14 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Jul 2005 00:10:14 -0700
X-ASF-Spam-Status: No, hits=0.4 required=10.0
tests=DNS_FROM_RFC_ABUSE
X-Spam-Check-By: apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Received: from [63.246.20.114] (HELO 63-246-20-114.contegix.com) (63.246.20.114)
by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Jul 2005 00:10:05 -0700
Received: (qmail 12486 invoked by uid 89); 20 Jul 2005 07:10:07 -0000
Received: from unknown (HELO codehaus01.managed.contegix.com) (127.0.0.1)
by smtp.domain.com with SMTP; 20 Jul 2005 07:10:07 -0000
Message-ID: <16...@codehaus01.managed.contegix.com>
Date: Wed, 20 Jul 2005 02:10:07 -0500 (CDT)
From: "Brett Porter (JIRA)" <ji...@codehaus.org>
To: dev@maven.apache.org
Subject: [jira] Updated: (MNG-479) unable to override the default central repository
In-Reply-To: <16...@codehaus01.managed.contegix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N
[ http://jira.codehaus.org/browse/MNG-479?page=all ]
Brett Porter updated MNG-479:
-----------------------------
Priority: Blocker (was: Minor)
> unable to override the default central repository
> -------------------------------------------------
>
> Key: MNG-479
> URL: http://jira.codehaus.org/browse/MNG-479
> Project: Maven 2
> Type: Bug
> Components: maven-core
> Versions: 2.0-alpha-2
> Environment: WinXP
> Reporter: Edwin Punzalan
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.0-beta-1
>
>
> Adding to my pom.xml:
> ....
> <repositories>
> <repository>
> <id>central</id>
> <name>custom repository</name>
> <url>http://maven.company.com/maven2</url>
> </repository>
> </repositories>
> ....
> did not override the central repository but instead uses the above configured repository as backup/mirror.
--
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
[jira] Updated: (MNG-384) make site reactor aware
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-384?page=all ]
Brett Porter updated MNG-384:
-----------------------------
Description:
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?
was:
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?
Fix Version: (was: 2.0-beta-1)
2.0-beta-2
Environment:
> make site reactor aware
> -----------------------
>
> Key: MNG-384
> URL: http://jira.codehaus.org/browse/MNG-384
> Project: Maven 2
> Type: Improvement
> Components: maven-plugins
> Versions: 2.0-alpha-2
> Reporter: Brett Porter
> Priority: Blocker
> Fix For: 2.0-beta-2
>
>
> 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
[jira] Commented: (MNG-384) make site reactor aware
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-384?page=comments#action_47227 ]
Brett Porter commented on MNG-384:
----------------------------------
I was thinking of holding this over until post-2.0 and discussing it at greater length when the pressure is off.
> 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
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.0-beta-3
>
>
> 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
[jira] Updated: (MSITE-44) make site reactor aware
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-44?page=all ]
Brett Porter updated MSITE-44:
------------------------------
Fix Version: 2.0
Remaining Estimate: 8 hours
Original Estimate: 8 hours
http://docs.codehaus.org/display/MAVEN/Sites+and+Inheritence
> 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
> Assignee: Brett Porter
> Priority: Blocker
> Fix For: 2.0
>
> Original Estimate: 8 hours
> Remaining: 8 hours
>
> 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
[jira] Commented: (MNG-384) make site reactor aware
Posted by "Fabrice BELLINGARD (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-384?page=comments#action_47337 ]
Fabrice BELLINGARD commented on MNG-384:
----------------------------------------
We're using site aggregation and dashboards of m1 widely in my company, and we want to switch from m1 to m2 ASAP though.
If maven 2.0 final release is to be "stable with a feature set comparable to Maven 1.0" - as we can read in announcements, don't you think those functionnalities should really be part of the 2.0 release? My development teams got used to dashboards of m1, and I guess they would be quite upset not to have it the final release of m2.
I perfectly understand that you have lots of things to do for final m2 though. I just wanted to share with you experiences and wishes of lots of Maven users of my company.
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-384) make site reactor aware
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-384?page=comments#action_47244 ]
John Casey commented on MNG-384:
--------------------------------
Agreed. I'll reschedule for 2.1.
> 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
> Assignee: John Casey
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MSITE-44) make site reactor aware
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-44?page=all ]
Brett Porter closed MSITE-44:
-----------------------------
Resolution: Fixed
> 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
> Assignee: Brett Porter
> Priority: Blocker
> Fix For: 2.0
>
> Original Estimate: 8 hours
> Time Spent: 16 hours
> Remaining: 0 minutes
>
> 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
[jira] Updated: (MNG-384) make site reactor aware
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-384?page=all ]
Brett Porter updated MNG-384:
-----------------------------
Component: (was: maven-plugins)
maven-site-plugin
> 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.0-beta-2
>
>
> 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
[jira] Commented: (MNG-384) make site reactor aware
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-384?page=comments#action_47216 ]
John Casey commented on MNG-384:
--------------------------------
I'm willing to take this one on, but I'm not sure how we're approaching dashboards and/or aggregation of report results. Does each report have the option to aggregate itself, or run as an aggregator itself? If so, would they be knocked out of the site-driven aggregation? Do we have a single dashboard plugin that we're developing, or is that a generic term?
Also, would we be performing a merge of site descriptors, as in nesting sub-project site.xml contents under a menu item in the parent? Does it make sense to attach the site.xml as an attached artifact and manage parent references using artifact resolution?
Sorry to throw out so many questions, but this is not a side of maven I've *ever* used much (not even in m1), so if I'm going to get this one fixed myself, I'll need some help.
> 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.0-beta-3
>
>
> 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
[jira] Commented: (MNG-384) make site reactor aware
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org