Re: Preparing for two releases of Maven Site Plugin
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 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 Might already be solved. MSITE-596 inheritedReports IT fails 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 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 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-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: For a mojo with requiresProject=false, I would like to avoid Maven from loading the pom.xml from working directory
On 04/17/2012 03:24 AM, Vincent Latombe wrote: Maven tries to parse the project and if it fails, it doesn't even call my mojo. Same applies to 'mvn archetype:generate'. Seems to me that this is a bug more than an RFE. Note that invocations of bin/mvn without a goal but with e.g. --encrypt-password do work even when $CWD/pom.xml exists and is invalid. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Next release of maven-release-plugin?
Hi all,
are there any chances to have a release of the maven-release-plugin in a
relatively short timeframe?
We're about to migrate a larger part of our build infrastructure to
Maven and would like to use MRELEASE-128 before we spread our proof of
concept into a wider scope.
It would help a lot if we could use properties in SCM connections, so we
can have even simpler project POMs and deduce the SCM connection strings
via a project-specific convention plus configuration in *one* parent
POM, like so:
connectionscm:svn:https://my.svnserver.local/repo/some-prefix/${project.groupId}/${project.artifactId}/trunk/connection
Thanks in advance for any answer.
Best regards
Ansgar
http://jira.codehaus.org/browse/MRELEASE-128
Preparation releases SCM 1.7 and MRELEASE 2.3
Hi, due to several RFR's (request for release) for the maven-release-plugin I'd first like to release SCM-1.7 first. For SCM 1.7[1] we have 10 issues fixed, 2 open and 1 reopened. All these open issues are assigned to Olivier. SCM-658: HgChangeLogCommand doesn't implement method executeChangeLogCommand(); blocker, bug, 0 votes SCM-623: Add a configuration mode to be able to use git svn (at least for release plugin) ; major, new feature, 4 votes SCM-656: Building maven-scm-1.6 requires a native install of git.; major, bug, 0 votes Olivier, could you judge these issues? If there are other issues which should be part of this release, please let me know. -Robert [1] http://jira.codehaus.org/browse/SCM/fixforversion/18136?selectedTab=com.atlassian.jira.plugin.system.project%3Aversion-issues-panel - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Preparation releases SCM 1.7 and MRELEASE 2.3
Hi, Yes it looks some people need m-r-p which depends on a new scm so I moved SCM-623 to 1.8 I will start release proces early next week. 2012/4/20 Robert Scholte apa...@sourcegrounds.com: Hi, due to several RFR's (request for release) for the maven-release-plugin I'd first like to release SCM-1.7 first. For SCM 1.7[1] we have 10 issues fixed, 2 open and 1 reopened. All these open issues are assigned to Olivier. SCM-658: HgChangeLogCommand doesn't implement method executeChangeLogCommand(); blocker, bug, 0 votes SCM-623: Add a configuration mode to be able to use git svn (at least for release plugin) ; major, new feature, 4 votes SCM-656: Building maven-scm-1.6 requires a native install of git.; major, bug, 0 votes Olivier, could you judge these issues? If there are other issues which should be part of this release, please let me know. -Robert [1] http://jira.codehaus.org/browse/SCM/fixforversion/18136?selectedTab=com.atlassian.jira.plugin.system.project%3Aversion-issues-panel - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
