On my side, I really would like to see MSITE-604 fixed, I've given it some thoughts today, and unfortunately I can only fix it for Maven 3, not for Maven 2 (because of MNG-1943 <http://jira.codehaus.org/browse/MNG-1943>that is only fixed with Maven 3). I've proposed a patch that is still work in progress (since I don't know a clean way to detect from this context whether we are in maven 2 or maven 3 context).
Vincent 2012/4/20 Lukas Theussl <ltheu...@apache.org> > > MSITE-601 is a wagon issue IIUC, the other issues can be delayed. > > Thanks Denis for doing this! > > -Lukas > > > > Robert Scholte wrote: > >> Hi Dennis, >> >> I don't see any blockers in Jira, only one critical (MSITE-601) but this >> seems to be a rare case, so I'd prefer to push that one to a later >> release too. >> MSITE-582 is confirmed by Hervé, an IT has been added. >> >> I'd expect that the new Doxia versions should result in a very enhanced >> version of the m-site-p. >> >> I don't see issues I'd like to pick up for this release. >> >> -Robert >> >> Op Wed, 18 Apr 2012 22:01:43 +0200 schreef Dennis Lundberg >> <denn...@apache.org>: >> >> Hi, >>> >>> Now that the Doxia releases are done, I'd like to focus on Maven Site >>> Plugin. We have two pending releases; 2.4 which will be the last release >>> of the 2.x series and then 3.1. >>> >>> Looking in JIRA, all the issues scheduled for 2.4 have been fixed and >>> closed. Does anyone want to add anything more to that release? If not, >>> I'll prepare the 2.4 release this weekend. >>> >>> When we look at the 3.1 release in JIRA there are 5 scheduled issues >>> that have not been solved. Here's a summary of them and how I'd like to >>> handle them: >>> >>> MSITE-484 Support adding and overriding report plugins in new >>> maven-site-plugin 3.x reportPlugins configuration format >>> http://jira.codehaus.org/**browse/MSITE-484<http://jira.codehaus.org/browse/MSITE-484> >>> This is a major issue that might require changes to Maven core. Push it >>> to later release. >>> >>> MSITE-582 Make it possible to remove breadcrumbs in child projects again >>> http://jira.codehaus.org/**browse/MSITE-582<http://jira.codehaus.org/browse/MSITE-582> >>> Might already be solved. >>> >>> MSITE-596 inheritedReports IT fails >>> http://jira.codehaus.org/**browse/MSITE-596<http://jira.codehaus.org/browse/MSITE-596> >>> Proposed solution requires changes to Maven core. Push to a later >>> release, but document the current behavior as per Lukas' comment. >>> >>> MSITE-601 Period added to URL prevents proper cloning with Mercurial >>> http://jira.codehaus.org/**browse/MSITE-601<http://jira.codehaus.org/browse/MSITE-601> >>> Unless someone has a patch for it, I'd like to unschedule it. >>> >>> MSITE-604 Properties from settings.xml are not recognized in site >>> distribution management >>> http://jira.codehaus.org/**browse/MSITE-604<http://jira.codehaus.org/browse/MSITE-604> >>> This is strangely related to MSITE-632, but I cannot find a suitable >>> solution to either of them. Push to a later release. >>> >>> >>> Do we want to add any more issues to the 3.1 release? >>> >>> >>> Please comment on this. >>> >> >> ------------------------------**------------------------------**--------- >> To unsubscribe, e-mail: >> dev-unsubscribe@maven.apache.**org<dev-unsubscr...@maven.apache.org> >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > dev-unsubscribe@maven.apache.**org<dev-unsubscr...@maven.apache.org> > For additional commands, e-mail: dev-h...@maven.apache.org > >
