maven release plugin introducing scm urls into modified poms
Hi All. I have a multi module project that I have working perfectly. In tracking down a reported problem, I ran the release plugin with the -DpreparationGoals=help:effective-pom clean verify In it, I can see that it has added a scm section into the poms in the modules. Although this is with Jazz, the same happens in SVN as well. The urls that are rewritten in the root pom are correctly. I've added the JazzScmTranslator into the release manager. It adds a /sub module name to the end of the URL, which in Jazz's case, makes no sense, but it will make sense for SVN - and it's correct. Is there a way to stop this? This only becomes a problem, when there is a scm section in a pom in one of the modules, as when it is written out, it is incorrect. Or is this an unsupported configuration? Ie, undefined behaviour? -Chris - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven release plugin introducing scm urls into modified poms
Am 20.02.2012 06:51 schrieb Chris Graham chrisgw...@gmail.com: Hi All. I have a multi module project that I have working perfectly. In tracking down a reported problem, I ran the release plugin with the -DpreparationGoals=help:effective-pom clean verify In it, I can see that it has added a scm section into the poms in the modules. Although this is with Jazz, the same happens in SVN as well. The urls that are rewritten in the root pom are correctly. I've added the JazzScmTranslator into the release manager. It adds a /sub module name to the end of the URL, which in Jazz's case, makes no sense, but it will make sense for SVN - and it's correct. Is there a way to stop this? Git also likes no submodule suffix in its scm urls. You could have a look at the git scm provider how it's implemented there. HTH Ansgar This only becomes a problem, when there is a scm section in a pom in one of the modules, as when it is written out, it is incorrect. Or is this an unsupported configuration? Ie, undefined behaviour? -Chris - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[maven-release-plugin] MRELEASE-459 waiting for review/commit
Hi, MRELEASE-459[1] has been in JIRA for over two years with a patch that seems sane. Any chance on getting this included? I'd be happy to do any further work required to get it in just not sure how to draw some attention to it. Cheers, Lars [1] http://jira.codehaus.org/browse/MRELEASE-459 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: svn commit: r1229755 - /maven/release/trunk/maven-release-plugin/src/main/java/org/apache/maven/plugins/release/AbstractReleaseMojo.java
Hi Simone,
simple answer: because the original code wasn't using the entryset. I only
added generics, verifying I didn't introduce a potential NPE with new
for-loops.
I haven't checked if the code could be optimized, but this looks like one.
-Robert
On Wed, 11 Jan 2012 08:57:17 +0100, Simone Tripodi
simonetrip...@apache.org wrote:
Hi Robert!
+for ( String providerType :
providerImplementations.keySet() )
{
-String providerType = (String) i.next();
-String providerImplementation = (String)
providerImplementations.get( providerType );
+String providerImplementation =
providerImplementations.get( providerType );
why not just iterating over providerImplementations.entrySet() ?
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
-
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: svn commit: r1229755 - /maven/release/trunk/maven-release-plugin/src/main/java/org/apache/maven/plugins/release/AbstractReleaseMojo.java
Hi Robert!
+ for ( String providerType : providerImplementations.keySet() )
{
- String providerType = (String) i.next();
- String providerImplementation = (String)
providerImplementations.get( providerType );
+ String providerImplementation = providerImplementations.get(
providerType );
why not just iterating over providerImplementations.entrySet() ?
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Hello, I will stage an other RC today evening time (fr tz) 2012/1/4 Stephen Connolly stephen.alan.conno...@gmail.com: cool - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 4 Jan 2012 20:58, Olivier Lamy ol...@apache.org wrote: Hello, it added and fix merged in RC branch. On irc, Robert remember me the upgrade of site plugin version for site lifecycle (was mentioned in a previous RC thread) I will add that too. As it's IMHO very low risk as mvn3.x users already add site plugin version in their pom to get site plugin working. 2012/1/4 Stephen Connolly stephen.alan.conno...@gmail.com: i have the fix written and on the 3.0.5 trunk... with some unit tests also. been trying to write a core it, but so far all my attempts have seemed too heavy to add to the test suite. - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 4 Jan 2012 08:34, Olivier Lamy ol...@apache.org wrote: 2012/1/4 Benson Margulies bimargul...@gmail.com: On Tue, Jan 3, 2012 at 6:12 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: also part of the problem in this specific case is that it is tricky to test the release plugin... i may look into refactoring the current tests to be based off of mrm-maven-plugin, as that should open up additional test paths. further i may add some multi-maven version testing so that the tests run against a couple of maven versions rather than just the invoking one. but for now we just have to live with the bug by either keeping to version 2.2.1 (of one of either maven or the release plugin) or wait until 3.0.5, or beat up olamy to backport the (fairly low risk) fix Good luck there. His wife just presented him with another offspring, a trifle ahead of schedule. Usually, this doesn't prevent to hack :-) Today or tomorrow, I will try to write a core it test for this issue and have a look at the changes to fix that. - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 3 Jan 2012 22:51, Brett Porter br...@apache.org wrote: On 04/01/2012, at 9:04 AM, Ansgar Konermann wrote: Am 03.01.2012 22:12, schrieb Benson Margulies: On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt m...@talios.com wrote: Surely something as egregious as allowing releases to break should block 3.0.4 from being released tho. As someone who uses GPG in that manner for some of his releases I'd certainly want 3.0.4 to be able to release... I disagree. There's no law requiring people to use 2.2.2 of the plugin. Hi, that's is an interesting point. No offense here, but what *is* the law w.r.t a Maven Release? I'm not that deep into Apache and Maven processes, but from what I could learn from public sources so far, I believe this is not clear altogether, and it might help to discuss this and make up our mind regarding such a law (i. e. release policy) to have a guideline for the future. Being a bit heretical: is it Maven's policy to release only Maven and wish the user luck to find out which versions of the core plugins work well with which version of Maven? Or can the average user expect to be reasonably safe if using the latest release of Maven with the latest release of any core plugin? From a user perspective, I perceive Maven as the Maven application plus its core plugins - they are basically one system. Agreed, it has a highly modular architecture, and a lot of these modules (= plugins) have decoupled release cycles, nevertheless it's IMHO hard to sell to the average user that the newest bugfix release of Maven with the newest bugfix release of the release plugin has *more* bugs than the slightly outdated one. We have a number of core plugins with versions set in the parent POM with each release. We use an unsophisticated metric to decide what to use: - been out for a while without reports of major projects - someone was motivated to update it They'll generally be very stable but may lag the latest releases - but you should consider those will all work well out of the box. It's on the plugin authors to test their plugins with different released versions of Maven and report on compatibility. For new Maven releases, we rely on the user community testing to identify any regressions with various different versions of plugins, so there's no blessed versions. If you're conservative, you might use the same policy we
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
2012/1/4 Benson Margulies bimargul...@gmail.com: On Tue, Jan 3, 2012 at 6:12 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: also part of the problem in this specific case is that it is tricky to test the release plugin... i may look into refactoring the current tests to be based off of mrm-maven-plugin, as that should open up additional test paths. further i may add some multi-maven version testing so that the tests run against a couple of maven versions rather than just the invoking one. but for now we just have to live with the bug by either keeping to version 2.2.1 (of one of either maven or the release plugin) or wait until 3.0.5, or beat up olamy to backport the (fairly low risk) fix Good luck there. His wife just presented him with another offspring, a trifle ahead of schedule. Usually, this doesn't prevent to hack :-) Today or tomorrow, I will try to write a core it test for this issue and have a look at the changes to fix that. - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 3 Jan 2012 22:51, Brett Porter br...@apache.org wrote: On 04/01/2012, at 9:04 AM, Ansgar Konermann wrote: Am 03.01.2012 22:12, schrieb Benson Margulies: On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt m...@talios.com wrote: Surely something as egregious as allowing releases to break should block 3.0.4 from being released tho. As someone who uses GPG in that manner for some of his releases I'd certainly want 3.0.4 to be able to release... I disagree. There's no law requiring people to use 2.2.2 of the plugin. Hi, that's is an interesting point. No offense here, but what *is* the law w.r.t a Maven Release? I'm not that deep into Apache and Maven processes, but from what I could learn from public sources so far, I believe this is not clear altogether, and it might help to discuss this and make up our mind regarding such a law (i. e. release policy) to have a guideline for the future. Being a bit heretical: is it Maven's policy to release only Maven and wish the user luck to find out which versions of the core plugins work well with which version of Maven? Or can the average user expect to be reasonably safe if using the latest release of Maven with the latest release of any core plugin? From a user perspective, I perceive Maven as the Maven application plus its core plugins - they are basically one system. Agreed, it has a highly modular architecture, and a lot of these modules (= plugins) have decoupled release cycles, nevertheless it's IMHO hard to sell to the average user that the newest bugfix release of Maven with the newest bugfix release of the release plugin has *more* bugs than the slightly outdated one. We have a number of core plugins with versions set in the parent POM with each release. We use an unsophisticated metric to decide what to use: - been out for a while without reports of major projects - someone was motivated to update it They'll generally be very stable but may lag the latest releases - but you should consider those will all work well out of the box. It's on the plugin authors to test their plugins with different released versions of Maven and report on compatibility. For new Maven releases, we rely on the user community testing to identify any regressions with various different versions of plugins, so there's no blessed versions. If you're conservative, you might use the same policy we use for the core plugins, though I'd speculate the people inclined to test the release probably tend to test with close to recent versions of plugins. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - 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 -- 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
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
i have the fix written and on the 3.0.5 trunk... with some unit tests also. been trying to write a core it, but so far all my attempts have seemed too heavy to add to the test suite. - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 4 Jan 2012 08:34, Olivier Lamy ol...@apache.org wrote: 2012/1/4 Benson Margulies bimargul...@gmail.com: On Tue, Jan 3, 2012 at 6:12 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: also part of the problem in this specific case is that it is tricky to test the release plugin... i may look into refactoring the current tests to be based off of mrm-maven-plugin, as that should open up additional test paths. further i may add some multi-maven version testing so that the tests run against a couple of maven versions rather than just the invoking one. but for now we just have to live with the bug by either keeping to version 2.2.1 (of one of either maven or the release plugin) or wait until 3.0.5, or beat up olamy to backport the (fairly low risk) fix Good luck there. His wife just presented him with another offspring, a trifle ahead of schedule. Usually, this doesn't prevent to hack :-) Today or tomorrow, I will try to write a core it test for this issue and have a look at the changes to fix that. - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 3 Jan 2012 22:51, Brett Porter br...@apache.org wrote: On 04/01/2012, at 9:04 AM, Ansgar Konermann wrote: Am 03.01.2012 22:12, schrieb Benson Margulies: On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt m...@talios.com wrote: Surely something as egregious as allowing releases to break should block 3.0.4 from being released tho. As someone who uses GPG in that manner for some of his releases I'd certainly want 3.0.4 to be able to release... I disagree. There's no law requiring people to use 2.2.2 of the plugin. Hi, that's is an interesting point. No offense here, but what *is* the law w.r.t a Maven Release? I'm not that deep into Apache and Maven processes, but from what I could learn from public sources so far, I believe this is not clear altogether, and it might help to discuss this and make up our mind regarding such a law (i. e. release policy) to have a guideline for the future. Being a bit heretical: is it Maven's policy to release only Maven and wish the user luck to find out which versions of the core plugins work well with which version of Maven? Or can the average user expect to be reasonably safe if using the latest release of Maven with the latest release of any core plugin? From a user perspective, I perceive Maven as the Maven application plus its core plugins - they are basically one system. Agreed, it has a highly modular architecture, and a lot of these modules (= plugins) have decoupled release cycles, nevertheless it's IMHO hard to sell to the average user that the newest bugfix release of Maven with the newest bugfix release of the release plugin has *more* bugs than the slightly outdated one. We have a number of core plugins with versions set in the parent POM with each release. We use an unsophisticated metric to decide what to use: - been out for a while without reports of major projects - someone was motivated to update it They'll generally be very stable but may lag the latest releases - but you should consider those will all work well out of the box. It's on the plugin authors to test their plugins with different released versions of Maven and report on compatibility. For new Maven releases, we rely on the user community testing to identify any regressions with various different versions of plugins, so there's no blessed versions. If you're conservative, you might use the same policy we use for the core plugins, though I'd speculate the people inclined to test the release probably tend to test with close to recent versions of plugins. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - 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 -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Hello, it added and fix merged in RC branch. On irc, Robert remember me the upgrade of site plugin version for site lifecycle (was mentioned in a previous RC thread) I will add that too. As it's IMHO very low risk as mvn3.x users already add site plugin version in their pom to get site plugin working. 2012/1/4 Stephen Connolly stephen.alan.conno...@gmail.com: i have the fix written and on the 3.0.5 trunk... with some unit tests also. been trying to write a core it, but so far all my attempts have seemed too heavy to add to the test suite. - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 4 Jan 2012 08:34, Olivier Lamy ol...@apache.org wrote: 2012/1/4 Benson Margulies bimargul...@gmail.com: On Tue, Jan 3, 2012 at 6:12 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: also part of the problem in this specific case is that it is tricky to test the release plugin... i may look into refactoring the current tests to be based off of mrm-maven-plugin, as that should open up additional test paths. further i may add some multi-maven version testing so that the tests run against a couple of maven versions rather than just the invoking one. but for now we just have to live with the bug by either keeping to version 2.2.1 (of one of either maven or the release plugin) or wait until 3.0.5, or beat up olamy to backport the (fairly low risk) fix Good luck there. His wife just presented him with another offspring, a trifle ahead of schedule. Usually, this doesn't prevent to hack :-) Today or tomorrow, I will try to write a core it test for this issue and have a look at the changes to fix that. - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 3 Jan 2012 22:51, Brett Porter br...@apache.org wrote: On 04/01/2012, at 9:04 AM, Ansgar Konermann wrote: Am 03.01.2012 22:12, schrieb Benson Margulies: On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt m...@talios.com wrote: Surely something as egregious as allowing releases to break should block 3.0.4 from being released tho. As someone who uses GPG in that manner for some of his releases I'd certainly want 3.0.4 to be able to release... I disagree. There's no law requiring people to use 2.2.2 of the plugin. Hi, that's is an interesting point. No offense here, but what *is* the law w.r.t a Maven Release? I'm not that deep into Apache and Maven processes, but from what I could learn from public sources so far, I believe this is not clear altogether, and it might help to discuss this and make up our mind regarding such a law (i. e. release policy) to have a guideline for the future. Being a bit heretical: is it Maven's policy to release only Maven and wish the user luck to find out which versions of the core plugins work well with which version of Maven? Or can the average user expect to be reasonably safe if using the latest release of Maven with the latest release of any core plugin? From a user perspective, I perceive Maven as the Maven application plus its core plugins - they are basically one system. Agreed, it has a highly modular architecture, and a lot of these modules (= plugins) have decoupled release cycles, nevertheless it's IMHO hard to sell to the average user that the newest bugfix release of Maven with the newest bugfix release of the release plugin has *more* bugs than the slightly outdated one. We have a number of core plugins with versions set in the parent POM with each release. We use an unsophisticated metric to decide what to use: - been out for a while without reports of major projects - someone was motivated to update it They'll generally be very stable but may lag the latest releases - but you should consider those will all work well out of the box. It's on the plugin authors to test their plugins with different released versions of Maven and report on compatibility. For new Maven releases, we rely on the user community testing to identify any regressions with various different versions of plugins, so there's no blessed versions. If you're conservative, you might use the same policy we use for the core plugins, though I'd speculate the people inclined to test the release probably tend to test with close to recent versions of plugins. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail:
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
cool - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 4 Jan 2012 20:58, Olivier Lamy ol...@apache.org wrote: Hello, it added and fix merged in RC branch. On irc, Robert remember me the upgrade of site plugin version for site lifecycle (was mentioned in a previous RC thread) I will add that too. As it's IMHO very low risk as mvn3.x users already add site plugin version in their pom to get site plugin working. 2012/1/4 Stephen Connolly stephen.alan.conno...@gmail.com: i have the fix written and on the 3.0.5 trunk... with some unit tests also. been trying to write a core it, but so far all my attempts have seemed too heavy to add to the test suite. - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 4 Jan 2012 08:34, Olivier Lamy ol...@apache.org wrote: 2012/1/4 Benson Margulies bimargul...@gmail.com: On Tue, Jan 3, 2012 at 6:12 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: also part of the problem in this specific case is that it is tricky to test the release plugin... i may look into refactoring the current tests to be based off of mrm-maven-plugin, as that should open up additional test paths. further i may add some multi-maven version testing so that the tests run against a couple of maven versions rather than just the invoking one. but for now we just have to live with the bug by either keeping to version 2.2.1 (of one of either maven or the release plugin) or wait until 3.0.5, or beat up olamy to backport the (fairly low risk) fix Good luck there. His wife just presented him with another offspring, a trifle ahead of schedule. Usually, this doesn't prevent to hack :-) Today or tomorrow, I will try to write a core it test for this issue and have a look at the changes to fix that. - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 3 Jan 2012 22:51, Brett Porter br...@apache.org wrote: On 04/01/2012, at 9:04 AM, Ansgar Konermann wrote: Am 03.01.2012 22:12, schrieb Benson Margulies: On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt m...@talios.com wrote: Surely something as egregious as allowing releases to break should block 3.0.4 from being released tho. As someone who uses GPG in that manner for some of his releases I'd certainly want 3.0.4 to be able to release... I disagree. There's no law requiring people to use 2.2.2 of the plugin. Hi, that's is an interesting point. No offense here, but what *is* the law w.r.t a Maven Release? I'm not that deep into Apache and Maven processes, but from what I could learn from public sources so far, I believe this is not clear altogether, and it might help to discuss this and make up our mind regarding such a law (i. e. release policy) to have a guideline for the future. Being a bit heretical: is it Maven's policy to release only Maven and wish the user luck to find out which versions of the core plugins work well with which version of Maven? Or can the average user expect to be reasonably safe if using the latest release of Maven with the latest release of any core plugin? From a user perspective, I perceive Maven as the Maven application plus its core plugins - they are basically one system. Agreed, it has a highly modular architecture, and a lot of these modules (= plugins) have decoupled release cycles, nevertheless it's IMHO hard to sell to the average user that the newest bugfix release of Maven with the newest bugfix release of the release plugin has *more* bugs than the slightly outdated one. We have a number of core plugins with versions set in the parent POM with each release. We use an unsophisticated metric to decide what to use: - been out for a while without reports of major projects - someone was motivated to update it They'll generally be very stable but may lag the latest releases - but you should consider those will all work well out of the box. It's on the plugin authors to test their plugins with different released versions of Maven and report on compatibility. For new Maven releases, we rely on the user community testing to identify any regressions with various different versions of plugins, so there's no blessed versions. If you're conservative, you might use the same policy we use for the core plugins, though I'd speculate the people inclined to test the release probably tend to test with close
WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Hi, I just found a regression: http://jira.codehaus.org/browse/MNG-5224 I think it is serious enough to recommend users avoid using the above combination if you rely on properties in a settings.xml profile to GPG sign your releases. (i.e. anyone pushing to Central) -Stephen - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Is this still broken under the 3.0.4-RC4 builds, or just 3.0.3? -- Great artists are extremely selfish and arrogant things — Steven Wilson, Porcupine Tree On Wed, Jan 4, 2012 at 4:18 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Hi, I just found a regression: http://jira.codehaus.org/browse/MNG-5224 I think it is serious enough to recommend users avoid using the above combination if you rely on properties in a settings.xml profile to GPG sign your releases. (i.e. anyone pushing to Central) -Stephen - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
I have checked in a fix towards 3.0.5... Pester olamy to backport... though he may want to wait for me to write the tests of the fix (manual testing confirms the fix... just have to figure out how to get automated testing!) On 3 January 2012 16:03, Mark Derricutt m...@talios.com wrote: Is this still broken under the 3.0.4-RC4 builds, or just 3.0.3? -- Great artists are extremely selfish and arrogant things — Steven Wilson, Porcupine Tree On Wed, Jan 4, 2012 at 4:18 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Hi, I just found a regression: http://jira.codehaus.org/browse/MNG-5224 I think it is serious enough to recommend users avoid using the above combination if you rely on properties in a settings.xml profile to GPG sign your releases. (i.e. anyone pushing to Central) -Stephen - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Surely something as egregious as allowing releases to break should block 3.0.4 from being released tho. As someone who uses GPG in that manner for some of his releases I'd certainly want 3.0.4 to be able to release... -- Great artists are extremely selfish and arrogant things — Steven Wilson, Porcupine Tree On Wed, Jan 4, 2012 at 5:23 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: I have checked in a fix towards 3.0.5... Pester olamy to backport... though he may want to wait for me to write the tests of the fix (manual testing confirms the fix... just have to figure out how to get automated testing!) On 3 January 2012 16:03, Mark Derricutt m...@talios.com wrote: Is this still broken under the 3.0.4-RC4 builds, or just 3.0.3? -- Great artists are extremely selfish and arrogant things — Steven Wilson, Porcupine Tree On Wed, Jan 4, 2012 at 4:18 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Hi, I just found a regression: http://jira.codehaus.org/browse/MNG-5224 I think it is serious enough to recommend users avoid using the above combination if you rely on properties in a settings.xml profile to GPG sign your releases. (i.e. anyone pushing to Central) -Stephen - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
it all depends on whether olamy decides as RM to backport or not. he is RM for the 3.0.4 release by virtue of action. On Tuesday, 3 January 2012, Mark Derricutt m...@talios.com wrote: Surely something as egregious as allowing releases to break should block 3.0.4 from being released tho. As someone who uses GPG in that manner for some of his releases I'd certainly want 3.0.4 to be able to release... -- Great artists are extremely selfish and arrogant things — Steven Wilson, Porcupine Tree On Wed, Jan 4, 2012 at 5:23 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: I have checked in a fix towards 3.0.5... Pester olamy to backport... though he may want to wait for me to write the tests of the fix (manual testing confirms the fix... just have to figure out how to get automated testing!) On 3 January 2012 16:03, Mark Derricutt m...@talios.com wrote: Is this still broken under the 3.0.4-RC4 builds, or just 3.0.3? -- Great artists are extremely selfish and arrogant things — Steven Wilson, Porcupine Tree On Wed, Jan 4, 2012 at 4:18 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Hi, I just found a regression: http://jira.codehaus.org/browse/MNG-5224 I think it is serious enough to recommend users avoid using the above combination if you rely on properties in a settings.xml profile to GPG sign your releases. (i.e. anyone pushing to Central) -Stephen - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Greetings, On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt m...@talios.com wrote: Surely something as egregious as allowing releases to break should block 3.0.4 from being released tho. As someone who uses GPG in that manner for some of his releases I'd certainly want 3.0.4 to be able to release... It didn't stop the 3.0.3 release, what's the difference with 3.0.4? It's getting rather frustrating at seeing all these relatively solitary or edge-case problems derail the entire release process. I have performed many releases with 3.0.3 and 3.0.4-rcX both, so this is not a problem for me, and I dare say it's a very large majority of users that it is also not a problem for. Stop stopping the presses, please!! It's just a stupid point release! It doesn't have to solve every existing MNG-* out there! This kind of localized Chicken Little behavior is making it harder and harder to get small releases out the door. You're making it worse for all users. *sigh* (the same goes for all the bike shedding whiners about the dependency fetch timeout - you know who you are) -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not.
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt m...@talios.com wrote: Surely something as egregious as allowing releases to break should block 3.0.4 from being released tho. As someone who uses GPG in that manner for some of his releases I'd certainly want 3.0.4 to be able to release... I disagree. There's no law requiring people to use 2.2.2 of the plugin. -- Great artists are extremely selfish and arrogant things — Steven Wilson, Porcupine Tree On Wed, Jan 4, 2012 at 5:23 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: I have checked in a fix towards 3.0.5... Pester olamy to backport... though he may want to wait for me to write the tests of the fix (manual testing confirms the fix... just have to figure out how to get automated testing!) On 3 January 2012 16:03, Mark Derricutt m...@talios.com wrote: Is this still broken under the 3.0.4-RC4 builds, or just 3.0.3? -- Great artists are extremely selfish and arrogant things — Steven Wilson, Porcupine Tree On Wed, Jan 4, 2012 at 4:18 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Hi, I just found a regression: http://jira.codehaus.org/browse/MNG-5224 I think it is serious enough to recommend users avoid using the above combination if you rely on properties in a settings.xml profile to GPG sign your releases. (i.e. anyone pushing to Central) -Stephen - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Not only properties like I explained it here : http://jira.codehaus.org/browse/MRELEASE-724 Arnaud On Tue, Jan 3, 2012 at 4:18 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Hi, I just found a regression: http://jira.codehaus.org/browse/MNG-5224 I think it is serious enough to recommend users avoid using the above combination if you rely on properties in a settings.xml profile to GPG sign your releases. (i.e. anyone pushing to Central) -Stephen - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
that is because you are using maven-release-plugin 2.2.1 switch to 2.2.2 and see how you feel - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 3 Jan 2012 20:58, Jesse Farinacci jie...@gmail.com wrote: Greetings, On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt m...@talios.com wrote: Surely something as egregious as allowing releases to break should block 3.0.4 from being released tho. As someone who uses GPG in that manner for some of his releases I'd certainly want 3.0.4 to be able to release... It didn't stop the 3.0.3 release, what's the difference with 3.0.4? It's getting rather frustrating at seeing all these relatively solitary or edge-case problems derail the entire release process. I have performed many releases with 3.0.3 and 3.0.4-rcX both, so this is not a problem for me, and I dare say it's a very large majority of users that it is also not a problem for. Stop stopping the presses, please!! It's just a stupid point release! It doesn't have to solve every existing MNG-* out there! This kind of localized Chicken Little behavior is making it harder and harder to get small releases out the door. You're making it worse for all users. *sigh* (the same goes for all the bike shedding whiners about the dependency fetch timeout - you know who you are) -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not.
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Hello, As it's not mandatory for users to use release plugin 2.2.2, no problem to release a 3.0.5 in 5/6 weeks. We must release this 3.0.4 one day... BTW could be nice to have both it tests for that in core it and in release plugin too ... 2012/1/3 Jesse Farinacci jie...@gmail.com: Greetings, On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt m...@talios.com wrote: Surely something as egregious as allowing releases to break should block 3.0.4 from being released tho. As someone who uses GPG in that manner for some of his releases I'd certainly want 3.0.4 to be able to release... It didn't stop the 3.0.3 release, what's the difference with 3.0.4? It's getting rather frustrating at seeing all these relatively solitary or edge-case problems derail the entire release process. I have performed many releases with 3.0.3 and 3.0.4-rcX both, so this is not a problem for me, and I dare say it's a very large majority of users that it is also not a problem for. Stop stopping the presses, please!! It's just a stupid point release! It doesn't have to solve every existing MNG-* out there! This kind of localized Chicken Little behavior is making it harder and harder to get small releases out the door. You're making it worse for all users. *sigh* (the same goes for all the bike shedding whiners about the dependency fetch timeout - you know who you are) -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not. -- 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
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Greetings, On Tue, Jan 3, 2012 at 4:20 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: that is because you are using maven-release-plugin 2.2.1 switch to 2.2.2 and see how you feel Sounds like there is a clear and easy work around. Why hold up a release for this? -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not.
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
I agree to not hold up the 3.0.4 release as it was already in 3.0.3 thus the problem was in the previous release process that didn't identify this problem. The problem of this bug is that we don't know if this bug is affecting many plugins but it seems that it's not really the case as it is here for a long time now (more than one year ago when we released the 3.0.3) I would recommend to try to improve the visibility of know bugs in our web sites (core and plugins) to try to avoid as much as possible to let our users loose many time with them. The question is how ??? For example for this bug with the release plugin I lost 1/2 day to identify it ( the time to understand that one team upgraded the release plugin version, to replay the release problem ...) Arnaud On Tue, Jan 3, 2012 at 10:29 PM, Jesse Farinacci jie...@gmail.com wrote: Greetings, On Tue, Jan 3, 2012 at 4:20 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: that is because you are using maven-release-plugin 2.2.1 switch to 2.2.2 and see how you feel Sounds like there is a clear and easy work around. Why hold up a release for this? -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not.
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
i am not saying hold up the release... just beware the combo - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 3 Jan 2012 21:22, Olivier Lamy ol...@apache.org wrote: Hello, As it's not mandatory for users to use release plugin 2.2.2, no problem to release a 3.0.5 in 5/6 weeks. We must release this 3.0.4 one day... BTW could be nice to have both it tests for that in core it and in release plugin too ... 2012/1/3 Jesse Farinacci jie...@gmail.com: Greetings, On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt m...@talios.com wrote: Surely something as egregious as allowing releases to break should block 3.0.4 from being released tho. As someone who uses GPG in that manner for some of his releases I'd certainly want 3.0.4 to be able to release... It didn't stop the 3.0.3 release, what's the difference with 3.0.4? It's getting rather frustrating at seeing all these relatively solitary or edge-case problems derail the entire release process. I have performed many releases with 3.0.3 and 3.0.4-rcX both, so this is not a problem for me, and I dare say it's a very large majority of users that it is also not a problem for. Stop stopping the presses, please!! It's just a stupid point release! It doesn't have to solve every existing MNG-* out there! This kind of localized Chicken Little behavior is making it harder and harder to get small releases out the door. You're making it worse for all users. *sigh* (the same goes for all the bike shedding whiners about the dependency fetch timeout - you know who you are) -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not. -- 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
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Am 03.01.2012 22:12, schrieb Benson Margulies: On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt m...@talios.com wrote: Surely something as egregious as allowing releases to break should block 3.0.4 from being released tho. As someone who uses GPG in that manner for some of his releases I'd certainly want 3.0.4 to be able to release... I disagree. There's no law requiring people to use 2.2.2 of the plugin. Hi, that's is an interesting point. No offense here, but what *is* the law w.r.t a Maven Release? I'm not that deep into Apache and Maven processes, but from what I could learn from public sources so far, I believe this is not clear altogether, and it might help to discuss this and make up our mind regarding such a law (i. e. release policy) to have a guideline for the future. Being a bit heretical: is it Maven's policy to release only Maven and wish the user luck to find out which versions of the core plugins work well with which version of Maven? Or can the average user expect to be reasonably safe if using the latest release of Maven with the latest release of any core plugin? From a user perspective, I perceive Maven as the Maven application plus its core plugins - they are basically one system. Agreed, it has a highly modular architecture, and a lot of these modules (= plugins) have decoupled release cycles, nevertheless it's IMHO hard to sell to the average user that the newest bugfix release of Maven with the newest bugfix release of the release plugin has *more* bugs than the slightly outdated one. This leads to another question: shouldn't we have system tests which make sure that common usage scenarios work with, say, the last N maven releases? That is: should plugins run their ITs against multiple versions of Maven? If so, how many versions should they go into the past? Or even better, shouldn't a *Maven* release trigger re-running the ITs of the most recent release of all core plugins', using the new Maven version? Add to this the fact that signing artifacts before deployment using gpg is mandatory for sync to central, so this is one of the more important use cases of the release plugin. Would love to hear more opinions on this. Best regards Ansgar - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
On 04/01/2012, at 7:58 AM, Jesse Farinacci wrote: Greetings, On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt m...@talios.com wrote: Surely something as egregious as allowing releases to break should block 3.0.4 from being released tho. As someone who uses GPG in that manner for some of his releases I'd certainly want 3.0.4 to be able to release... It didn't stop the 3.0.3 release, what's the difference with 3.0.4? It's getting rather frustrating at seeing all these relatively solitary or edge-case problems derail the entire release process. I have performed many releases with 3.0.3 and 3.0.4-rcX both, so this is not a problem for me, and I dare say it's a very large majority of users that it is also not a problem for. Stop stopping the presses, please!! It's just a stupid point release! It doesn't have to solve every existing MNG-* out there! This kind of localized Chicken Little behavior is making it harder and harder to get small releases out the door. You're making it worse for all users. *sigh* (the same goes for all the bike shedding whiners about the dependency fetch timeout - you know who you are) That'd be me :) While I agree with your earlier reasoning in this case, there's a difference between a bug affecting a small subset of users that's been there for a few releases and an unexpected change in behaviour from the last release that would affect quite a few users... - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
On 04/01/2012, at 9:04 AM, Ansgar Konermann wrote: Am 03.01.2012 22:12, schrieb Benson Margulies: On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt m...@talios.com wrote: Surely something as egregious as allowing releases to break should block 3.0.4 from being released tho. As someone who uses GPG in that manner for some of his releases I'd certainly want 3.0.4 to be able to release... I disagree. There's no law requiring people to use 2.2.2 of the plugin. Hi, that's is an interesting point. No offense here, but what *is* the law w.r.t a Maven Release? I'm not that deep into Apache and Maven processes, but from what I could learn from public sources so far, I believe this is not clear altogether, and it might help to discuss this and make up our mind regarding such a law (i. e. release policy) to have a guideline for the future. Being a bit heretical: is it Maven's policy to release only Maven and wish the user luck to find out which versions of the core plugins work well with which version of Maven? Or can the average user expect to be reasonably safe if using the latest release of Maven with the latest release of any core plugin? From a user perspective, I perceive Maven as the Maven application plus its core plugins - they are basically one system. Agreed, it has a highly modular architecture, and a lot of these modules (= plugins) have decoupled release cycles, nevertheless it's IMHO hard to sell to the average user that the newest bugfix release of Maven with the newest bugfix release of the release plugin has *more* bugs than the slightly outdated one. We have a number of core plugins with versions set in the parent POM with each release. We use an unsophisticated metric to decide what to use: - been out for a while without reports of major projects - someone was motivated to update it They'll generally be very stable but may lag the latest releases - but you should consider those will all work well out of the box. It's on the plugin authors to test their plugins with different released versions of Maven and report on compatibility. For new Maven releases, we rely on the user community testing to identify any regressions with various different versions of plugins, so there's no blessed versions. If you're conservative, you might use the same policy we use for the core plugins, though I'd speculate the people inclined to test the release probably tend to test with close to recent versions of plugins. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
also part of the problem in this specific case is that it is tricky to test the release plugin... i may look into refactoring the current tests to be based off of mrm-maven-plugin, as that should open up additional test paths. further i may add some multi-maven version testing so that the tests run against a couple of maven versions rather than just the invoking one. but for now we just have to live with the bug by either keeping to version 2.2.1 (of one of either maven or the release plugin) or wait until 3.0.5, or beat up olamy to backport the (fairly low risk) fix - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 3 Jan 2012 22:51, Brett Porter br...@apache.org wrote: On 04/01/2012, at 9:04 AM, Ansgar Konermann wrote: Am 03.01.2012 22:12, schrieb Benson Margulies: On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt m...@talios.com wrote: Surely something as egregious as allowing releases to break should block 3.0.4 from being released tho. As someone who uses GPG in that manner for some of his releases I'd certainly want 3.0.4 to be able to release... I disagree. There's no law requiring people to use 2.2.2 of the plugin. Hi, that's is an interesting point. No offense here, but what *is* the law w.r.t a Maven Release? I'm not that deep into Apache and Maven processes, but from what I could learn from public sources so far, I believe this is not clear altogether, and it might help to discuss this and make up our mind regarding such a law (i. e. release policy) to have a guideline for the future. Being a bit heretical: is it Maven's policy to release only Maven and wish the user luck to find out which versions of the core plugins work well with which version of Maven? Or can the average user expect to be reasonably safe if using the latest release of Maven with the latest release of any core plugin? From a user perspective, I perceive Maven as the Maven application plus its core plugins - they are basically one system. Agreed, it has a highly modular architecture, and a lot of these modules (= plugins) have decoupled release cycles, nevertheless it's IMHO hard to sell to the average user that the newest bugfix release of Maven with the newest bugfix release of the release plugin has *more* bugs than the slightly outdated one. We have a number of core plugins with versions set in the parent POM with each release. We use an unsophisticated metric to decide what to use: - been out for a while without reports of major projects - someone was motivated to update it They'll generally be very stable but may lag the latest releases - but you should consider those will all work well out of the box. It's on the plugin authors to test their plugins with different released versions of Maven and report on compatibility. For new Maven releases, we rely on the user community testing to identify any regressions with various different versions of plugins, so there's no blessed versions. If you're conservative, you might use the same policy we use for the core plugins, though I'd speculate the people inclined to test the release probably tend to test with close to recent versions of plugins. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
On Tue, Jan 3, 2012 at 6:12 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: also part of the problem in this specific case is that it is tricky to test the release plugin... i may look into refactoring the current tests to be based off of mrm-maven-plugin, as that should open up additional test paths. further i may add some multi-maven version testing so that the tests run against a couple of maven versions rather than just the invoking one. but for now we just have to live with the bug by either keeping to version 2.2.1 (of one of either maven or the release plugin) or wait until 3.0.5, or beat up olamy to backport the (fairly low risk) fix Good luck there. His wife just presented him with another offspring, a trifle ahead of schedule. - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 3 Jan 2012 22:51, Brett Porter br...@apache.org wrote: On 04/01/2012, at 9:04 AM, Ansgar Konermann wrote: Am 03.01.2012 22:12, schrieb Benson Margulies: On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt m...@talios.com wrote: Surely something as egregious as allowing releases to break should block 3.0.4 from being released tho. As someone who uses GPG in that manner for some of his releases I'd certainly want 3.0.4 to be able to release... I disagree. There's no law requiring people to use 2.2.2 of the plugin. Hi, that's is an interesting point. No offense here, but what *is* the law w.r.t a Maven Release? I'm not that deep into Apache and Maven processes, but from what I could learn from public sources so far, I believe this is not clear altogether, and it might help to discuss this and make up our mind regarding such a law (i. e. release policy) to have a guideline for the future. Being a bit heretical: is it Maven's policy to release only Maven and wish the user luck to find out which versions of the core plugins work well with which version of Maven? Or can the average user expect to be reasonably safe if using the latest release of Maven with the latest release of any core plugin? From a user perspective, I perceive Maven as the Maven application plus its core plugins - they are basically one system. Agreed, it has a highly modular architecture, and a lot of these modules (= plugins) have decoupled release cycles, nevertheless it's IMHO hard to sell to the average user that the newest bugfix release of Maven with the newest bugfix release of the release plugin has *more* bugs than the slightly outdated one. We have a number of core plugins with versions set in the parent POM with each release. We use an unsophisticated metric to decide what to use: - been out for a while without reports of major projects - someone was motivated to update it They'll generally be very stable but may lag the latest releases - but you should consider those will all work well out of the box. It's on the plugin authors to test their plugins with different released versions of Maven and report on compatibility. For new Maven releases, we rely on the user community testing to identify any regressions with various different versions of plugins, so there's no blessed versions. If you're conservative, you might use the same policy we use for the core plugins, though I'd speculate the people inclined to test the release probably tend to test with close to recent versions of plugins. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - 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: Maven release plugin not honoring -Darguments
Am 27.09.2011 14:48 schrieb David Blevins david.blev...@gmail.com: Is it a known issue that the release plugin does not honor the -Darguments? Specifically, I'm attempting to: mvn release:prepare -DdryRun=true -Darguments=-DskipTests=true -DfailIfNoTests=false Try: mvn release:prepare -DdryRun=true -Darguments=-DskipTests=true -DfailIfNoTests=false Notice the slightly different quoting (before -Darguments). Works well for me. Best regards Ansgar It takes 40 minutes to get through a dryRun with tests on. We still have several kinks in the build to work out before the release plugin will work, so obviously running with tests on every dryRun is just making a hard task impossible. maven 3.0.3, apache-10 parent pom, maven-release-plugin 2.1 -David - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven release plugin not honoring -Darguments
This situation was discussed once before. The author of this pom, as I
recall, had pretty strong feelings about it.
You can work with it by making your own profile named apache_release
that has the additional stuff you want, or by overriding the execution
configuration in your pom to use your preferred arguments/.
On Thu, Dec 29, 2011 at 10:18 PM, David Blevins david.blev...@gmail.com wrote:
On Tue, Sep 27, 2011 at 1:09 PM, David Blevins david.blev...@gmail.com
wrote:
Did some more digging and it seems the issue is in the apache-10 parent pom.
If you alter it like so, the arguments are passed as expected:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
version2.1/version
configuration
useReleaseProfilefalse/useReleaseProfile
goalsdeploy/goals
!--arguments-Papache-release/arguments--
arguments-Papache-release ${arguments}/arguments
/configuration
/plugin
Seems this is just a mistake as the full config as reported via -X contains
quite a bit of foo${foo}/foo style declarations. We likely just missed
it here.
Going to use a hacked parent pom for the moment but it would be great if we
could get an apache-11 pom out soonish.
This came up again. Posting so I don't forget to deal with it when I
have time. Will file an issue with a patch tomorrow unless someone
beats me to it.
-David
-
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: Maven release plugin not honoring -Darguments
An FYI on the escaping/quoting as that's come up twice and isn't the issue.
public class Arguments {
public static void main(String[] args) {
for (String arg : args) {
System.out.printf([%s], arg);
}
System.out.println();
}
}
$ java Arguments mvn release:prepare -DdryRun=true
-Darguments=-DskipTests=true -DfailIfNoTests=false
[mvn][release:prepare][-DdryRun=true][-Darguments=-DskipTests=true
-DfailIfNoTests=false]
$ java Arguments mvn release:prepare -DdryRun=true
-Darguments=-DskipTests=true -DfailIfNoTests=false
[mvn][release:prepare][-DdryRun=true][-Darguments=-DskipTests=true
-DfailIfNoTests=false]
$ java Arguments mvn release:prepare -DdryRun=true
-Darguments=-DskipTests=true -DfailIfNoTests=false
[mvn][release:prepare][-DdryRun=true][-Darguments=-DskipTests=true
-DfailIfNoTests=false]
$ java Arguments mvn release:prepare -DdryRun=true
-Darguments=-DskipTests=true' '-DfailIfNoTests=false
[mvn][release:prepare][-DdryRun=true][-Darguments=-DskipTests=true
-DfailIfNoTests=false]
$ java Arguments mvn release:prepare -DdryRun=true
-Darguments=-DskipTests=true\ -DfailIfNoTests=false
[mvn][release:prepare][-DdryRun=true][-Darguments=-DskipTests=true
-DfailIfNoTests=false]
The next one just to be goofy :)
$ java Arguments mvn release:prepare -DdryRun=true
-Dargum'en'ts=-Ds'k'ipTests=true\ -DfailIfNoTest's'=false
[mvn][release:prepare][-DdryRun=true][-Darguments=-DskipTests=true
-DfailIfNoTests=false]
And finally an actually broken one:
$ java Arguments mvn release:prepare -DdryRun=true -Darguments=-DskipTests=true
-DfailIfNoTests=false
[mvn][release:prepare][-DdryRun=true][-Darguments=-DskipTests=true][-DfailIfNoTests=false]
The problem isn't with the plugin but the Apache parent pom. Thanks, Benson,
for the feedback on that. There're half dozen committers on that pom so I'm
not sure who has the objection to allowing -Darguments to be used.
I've created this jira and attached a patch. Hopefully we can either fix it or
document it as intentionally not working and give reasons and workarounds like
the ones you suggest. I'm fine with either outcome.
https://issues.apache.org/jira/browse/MPOM-35
On a side note,... Happy new year to all! :)
-David
On Dec 30, 2011, at 2:22 AM, Ansgar Konermann wrote:
Am 27.09.2011 14:48 schrieb David Blevins david.blev...@gmail.com:
Is it a known issue that the release plugin does not honor the
-Darguments?
Specifically, I'm attempting to:
mvn release:prepare -DdryRun=true -Darguments=-DskipTests=true
-DfailIfNoTests=false
Try:
mvn release:prepare -DdryRun=true -Darguments=-DskipTests=true
-DfailIfNoTests=false
Notice the slightly different quoting (before -Darguments). Works well for
me.
Best regards
Ansgar
It takes 40 minutes to get through a dryRun with tests on. We still have
several kinks in the build to work out before the release plugin will work,
so obviously running with tests on every dryRun is just making a hard task
impossible.
maven 3.0.3, apache-10 parent pom, maven-release-plugin 2.1
-David
-
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: Maven release plugin not honoring -Darguments
On Tue, Sep 27, 2011 at 1:09 PM, David Blevins david.blev...@gmail.com wrote:
Did some more digging and it seems the issue is in the apache-10 parent pom.
If you alter it like so, the arguments are passed as expected:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
version2.1/version
configuration
useReleaseProfilefalse/useReleaseProfile
goalsdeploy/goals
!--arguments-Papache-release/arguments--
arguments-Papache-release ${arguments}/arguments
/configuration
/plugin
Seems this is just a mistake as the full config as reported via -X contains
quite a bit of foo${foo}/foo style declarations. We likely just missed
it here.
Going to use a hacked parent pom for the moment but it would be great if we
could get an apache-11 pom out soonish.
This came up again. Posting so I don't forget to deal with it when I
have time. Will file an issue with a patch tomorrow unless someone
beats me to it.
-David
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-release-plugin: using git where do I see the tag used to build the release in the pom?
Hello, I erroneously opened the issue in the SCM plugin (https://jira.codehaus.org/browse/SCM-655), however it is an issue of MRELEASE probably. Would someone with the according rights move it to http://jira.codehaus.org/browse/MRELEASE, please? Best regards Mirko On Mon, Dec 19, 2011 at 22:56, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Then it will have to be the tag name so... On 19 December 2011 21:28, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Hm, this will be a hard one. I know detected, that the rewrite of the SCM section happens in the maven-release-plugin (org.apache.maven.shared.release.phase.RewritePomsForReleasePhase). Two problemes I encountered now: - The maven-scm-plugin does not seem to implement the equivalent of scm:info (there is an implementation in the maven-scm-api, however). - Providing the hash value instead of the symbolic release tag is kind of a chicken-egg scenario: we know the hash only after the rewrite of the pom and the commit, modifying the pom afterwards to include the hash as tag however does create a new hash. So inserting the hash seems to be impossible :-(. Any thoughts :-)? Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ On Mon, Dec 19, 2011 at 12:26, Olivier Lamy ol...@apache.org wrote: some scm providers have something implemented. for git it's : git rev-parse --verify HEAD for svn: svn info for hg: hg id more details on those providers in various Info command impls. 2011/12/19 Stephen Connolly stephen.alan.conno...@gmail.com: On 19 December 2011 10:45, Mirko Friedenhagen mfriedenha...@gmail.com wrote: As discussed on the user-list: On Fri, Dec 16, 2011 at 22:58, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Hello, I know that with SVN the developerConnection and connection are updated to the real URL, that is when I invoke release:prepare with a URL like: https://SVNSERVER/svn/REPO/myproject/branches/release it will be replaced by https://SVNSERVER/svn/REPO/myproject/tags/myproject-1.0 which is fine because now I know which revision to checkout for building the release. With git there is no such possibility to realize this with rewriting the URL AFAIK. So I would have expected however, that maybe the tag element would be updated to reflect the fact, that the pom is the one of release, either to the symbolic name myproject-1.0 or to the hash of the tag. Regards Mirko I opened http://jira.codehaus.org/browse/SCM-655. As I want give it a try to implement this (at least for GIT) two questions now: - What is preferable, symbolic tag name or hash? I fear it has to be hash but better would be to have it configurable - Is is feasible to implement such behavior in one provider only or should it be part of all (DVCS-)providers? When you've sent me the pony, then implement it for all DVCS providers and check that it is implemented for CVS too Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ - 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 -- 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 - 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
RE: maven-release-plugin: using git where do I see the tag used to build the release in the pom?
https://jira.codehaus.org/browse/MRELEASE-723 From: mfriedenha...@gmail.com Date: Tue, 20 Dec 2011 21:14:59 +0100 Subject: Re: maven-release-plugin: using git where do I see the tag used to build the release in the pom? To: dev@maven.apache.org Hello, I erroneously opened the issue in the SCM plugin (https://jira.codehaus.org/browse/SCM-655), however it is an issue of MRELEASE probably. Would someone with the according rights move it to http://jira.codehaus.org/browse/MRELEASE, please? Best regards Mirko On Mon, Dec 19, 2011 at 22:56, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Then it will have to be the tag name so... On 19 December 2011 21:28, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Hm, this will be a hard one. I know detected, that the rewrite of the SCM section happens in the maven-release-plugin (org.apache.maven.shared.release.phase.RewritePomsForReleasePhase). Two problemes I encountered now: - The maven-scm-plugin does not seem to implement the equivalent of scm:info (there is an implementation in the maven-scm-api, however). - Providing the hash value instead of the symbolic release tag is kind of a chicken-egg scenario: we know the hash only after the rewrite of the pom and the commit, modifying the pom afterwards to include the hash as tag however does create a new hash. So inserting the hash seems to be impossible :-(. Any thoughts :-)? Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ On Mon, Dec 19, 2011 at 12:26, Olivier Lamy ol...@apache.org wrote: some scm providers have something implemented. for git it's : git rev-parse --verify HEAD for svn: svn info for hg: hg id more details on those providers in various Info command impls. 2011/12/19 Stephen Connolly stephen.alan.conno...@gmail.com: On 19 December 2011 10:45, Mirko Friedenhagen mfriedenha...@gmail.com wrote: As discussed on the user-list: On Fri, Dec 16, 2011 at 22:58, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Hello, I know that with SVN the developerConnection and connection are updated to the real URL, that is when I invoke release:prepare with a URL like: https://SVNSERVER/svn/REPO/myproject/branches/release it will be replaced by https://SVNSERVER/svn/REPO/myproject/tags/myproject-1.0 which is fine because now I know which revision to checkout for building the release. With git there is no such possibility to realize this with rewriting the URL AFAIK. So I would have expected however, that maybe the tag element would be updated to reflect the fact, that the pom is the one of release, either to the symbolic name myproject-1.0 or to the hash of the tag. Regards Mirko I opened http://jira.codehaus.org/browse/SCM-655. As I want give it a try to implement this (at least for GIT) two questions now: - What is preferable, symbolic tag name or hash? I fear it has to be hash but better would be to have it configurable - Is is feasible to implement such behavior in one provider only or should it be part of all (DVCS-)providers? When you've sent me the pony, then implement it for all DVCS providers and check that it is implemented for CVS too Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ - 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 -- 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 - 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-release-plugin: using git where do I see the tag used to build the release in the pom?
As discussed on the user-list: On Fri, Dec 16, 2011 at 22:58, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Hello, I know that with SVN the developerConnection and connection are updated to the real URL, that is when I invoke release:prepare with a URL like: https://SVNSERVER/svn/REPO/myproject/branches/release it will be replaced by https://SVNSERVER/svn/REPO/myproject/tags/myproject-1.0 which is fine because now I know which revision to checkout for building the release. With git there is no such possibility to realize this with rewriting the URL AFAIK. So I would have expected however, that maybe the tag element would be updated to reflect the fact, that the pom is the one of release, either to the symbolic name myproject-1.0 or to the hash of the tag. Regards Mirko I opened http://jira.codehaus.org/browse/SCM-655. As I want give it a try to implement this (at least for GIT) two questions now: - What is preferable, symbolic tag name or hash? - Is is feasible to implement such behavior in one provider only or should it be part of all (DVCS-)providers? Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-release-plugin: using git where do I see the tag used to build the release in the pom?
On 19 December 2011 10:45, Mirko Friedenhagen mfriedenha...@gmail.com wrote: As discussed on the user-list: On Fri, Dec 16, 2011 at 22:58, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Hello, I know that with SVN the developerConnection and connection are updated to the real URL, that is when I invoke release:prepare with a URL like: https://SVNSERVER/svn/REPO/myproject/branches/release it will be replaced by https://SVNSERVER/svn/REPO/myproject/tags/myproject-1.0 which is fine because now I know which revision to checkout for building the release. With git there is no such possibility to realize this with rewriting the URL AFAIK. So I would have expected however, that maybe the tag element would be updated to reflect the fact, that the pom is the one of release, either to the symbolic name myproject-1.0 or to the hash of the tag. Regards Mirko I opened http://jira.codehaus.org/browse/SCM-655. As I want give it a try to implement this (at least for GIT) two questions now: - What is preferable, symbolic tag name or hash? I fear it has to be hash but better would be to have it configurable - Is is feasible to implement such behavior in one provider only or should it be part of all (DVCS-)providers? When you've sent me the pony, then implement it for all DVCS providers and check that it is implemented for CVS too Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ - 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: maven-release-plugin: using git where do I see the tag used to build the release in the pom?
some scm providers have something implemented. for git it's : git rev-parse --verify HEAD for svn: svn info for hg: hg id more details on those providers in various Info command impls. 2011/12/19 Stephen Connolly stephen.alan.conno...@gmail.com: On 19 December 2011 10:45, Mirko Friedenhagen mfriedenha...@gmail.com wrote: As discussed on the user-list: On Fri, Dec 16, 2011 at 22:58, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Hello, I know that with SVN the developerConnection and connection are updated to the real URL, that is when I invoke release:prepare with a URL like: https://SVNSERVER/svn/REPO/myproject/branches/release it will be replaced by https://SVNSERVER/svn/REPO/myproject/tags/myproject-1.0 which is fine because now I know which revision to checkout for building the release. With git there is no such possibility to realize this with rewriting the URL AFAIK. So I would have expected however, that maybe the tag element would be updated to reflect the fact, that the pom is the one of release, either to the symbolic name myproject-1.0 or to the hash of the tag. Regards Mirko I opened http://jira.codehaus.org/browse/SCM-655. As I want give it a try to implement this (at least for GIT) two questions now: - What is preferable, symbolic tag name or hash? I fear it has to be hash but better would be to have it configurable - Is is feasible to implement such behavior in one provider only or should it be part of all (DVCS-)providers? When you've sent me the pony, then implement it for all DVCS providers and check that it is implemented for CVS too Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ - 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 -- 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
Re: maven-release-plugin: using git where do I see the tag used to build the release in the pom?
Hm, this will be a hard one. I know detected, that the rewrite of the SCM section happens in the maven-release-plugin (org.apache.maven.shared.release.phase.RewritePomsForReleasePhase). Two problemes I encountered now: - The maven-scm-plugin does not seem to implement the equivalent of scm:info (there is an implementation in the maven-scm-api, however). - Providing the hash value instead of the symbolic release tag is kind of a chicken-egg scenario: we know the hash only after the rewrite of the pom and the commit, modifying the pom afterwards to include the hash as tag however does create a new hash. So inserting the hash seems to be impossible :-(. Any thoughts :-)? Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ On Mon, Dec 19, 2011 at 12:26, Olivier Lamy ol...@apache.org wrote: some scm providers have something implemented. for git it's : git rev-parse --verify HEAD for svn: svn info for hg: hg id more details on those providers in various Info command impls. 2011/12/19 Stephen Connolly stephen.alan.conno...@gmail.com: On 19 December 2011 10:45, Mirko Friedenhagen mfriedenha...@gmail.com wrote: As discussed on the user-list: On Fri, Dec 16, 2011 at 22:58, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Hello, I know that with SVN the developerConnection and connection are updated to the real URL, that is when I invoke release:prepare with a URL like: https://SVNSERVER/svn/REPO/myproject/branches/release it will be replaced by https://SVNSERVER/svn/REPO/myproject/tags/myproject-1.0 which is fine because now I know which revision to checkout for building the release. With git there is no such possibility to realize this with rewriting the URL AFAIK. So I would have expected however, that maybe the tag element would be updated to reflect the fact, that the pom is the one of release, either to the symbolic name myproject-1.0 or to the hash of the tag. Regards Mirko I opened http://jira.codehaus.org/browse/SCM-655. As I want give it a try to implement this (at least for GIT) two questions now: - What is preferable, symbolic tag name or hash? I fear it has to be hash but better would be to have it configurable - Is is feasible to implement such behavior in one provider only or should it be part of all (DVCS-)providers? When you've sent me the pony, then implement it for all DVCS providers and check that it is implemented for CVS too Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ - 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 -- 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-release-plugin: using git where do I see the tag used to build the release in the pom?
Then it will have to be the tag name so... On 19 December 2011 21:28, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Hm, this will be a hard one. I know detected, that the rewrite of the SCM section happens in the maven-release-plugin (org.apache.maven.shared.release.phase.RewritePomsForReleasePhase). Two problemes I encountered now: - The maven-scm-plugin does not seem to implement the equivalent of scm:info (there is an implementation in the maven-scm-api, however). - Providing the hash value instead of the symbolic release tag is kind of a chicken-egg scenario: we know the hash only after the rewrite of the pom and the commit, modifying the pom afterwards to include the hash as tag however does create a new hash. So inserting the hash seems to be impossible :-(. Any thoughts :-)? Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ On Mon, Dec 19, 2011 at 12:26, Olivier Lamy ol...@apache.org wrote: some scm providers have something implemented. for git it's : git rev-parse --verify HEAD for svn: svn info for hg: hg id more details on those providers in various Info command impls. 2011/12/19 Stephen Connolly stephen.alan.conno...@gmail.com: On 19 December 2011 10:45, Mirko Friedenhagen mfriedenha...@gmail.com wrote: As discussed on the user-list: On Fri, Dec 16, 2011 at 22:58, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Hello, I know that with SVN the developerConnection and connection are updated to the real URL, that is when I invoke release:prepare with a URL like: https://SVNSERVER/svn/REPO/myproject/branches/release it will be replaced by https://SVNSERVER/svn/REPO/myproject/tags/myproject-1.0 which is fine because now I know which revision to checkout for building the release. With git there is no such possibility to realize this with rewriting the URL AFAIK. So I would have expected however, that maybe the tag element would be updated to reflect the fact, that the pom is the one of release, either to the symbolic name myproject-1.0 or to the hash of the tag. Regards Mirko I opened http://jira.codehaus.org/browse/SCM-655. As I want give it a try to implement this (at least for GIT) two questions now: - What is preferable, symbolic tag name or hash? I fear it has to be hash but better would be to have it configurable - Is is feasible to implement such behavior in one provider only or should it be part of all (DVCS-)providers? When you've sent me the pony, then implement it for all DVCS providers and check that it is implemented for CVS too Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ - 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 -- 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 - 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: [ANN] Maven Release Plugin 2.2.2 Released
my bad. i forgot to fill in all the bits of the template! - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 17 Dec 2011 04:25, Wayne Fay wayne...@gmail.com wrote: That should have been: The Maven team is pleased to announce the release of the Maven 2.x Release Plugin, version 2.2.2 Wayne On 12/16/11, sebb seb...@gmail.com wrote: On 17 December 2011 01:46, Stephen Connolly steph...@apache.org wrote: The Maven team is pleased to announce the release of the Maven XXX Plugin, version Y.Z X, Y Z? This plugin is used to release a project with Maven, saving a lot of repetitive, manual work. Releasing a project is made in two steps: prepare and perform. http://maven.apache.org/plugins/maven-release-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version2.2.2/version /plugin Release Notes - Maven 2.x Release Plugin - Version 2.2.2 ** Bug * [MRELEASE-354] - Versions defined in profiles are not updated * [MRELEASE-454] - The Release-Plugin does not rewrite dependencies in the DependencyManagement with scope import * [MRELEASE-577] - release:prepare does not pass argument --settings with current settings.xml to inner maven ** Improvement * [MRELEASE-708] - upgrade to last scm 1.6 to integrate new scm provider mks integrity ** New Feature * [MRELEASE-467] - Release preparation should update version of plugin dependencies Enjoy, -The Maven team - 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Release Plugin version 2.2.2
+1 2011/12/13 Stephen Connolly stephen.alan.conno...@gmail.com: Hi, We solved 5 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=18224 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11144status=1 Staging repo: https://repository.apache.org/content/repositories/maven-326/ Staging site: http://maven.apache.org/plugins/maven-release-plugin-2.2.2/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -Stephen Note: * Beware the Sync... if you don't know how to setup proxies, you may have to wait up to 24h to see the staged site - 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
Re: [VOTE] Release Maven Release Plugin version 2.2.2
On Tue, 13 Dec 2011 17:20:52 + Stephen Connolly stephen.alan.conno...@gmail.com wrote: +1 (nonbinding) thanks. Tony. Hi, We solved 5 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=18224 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11144status=1 Staging repo: https://repository.apache.org/content/repositories/maven-326/ Staging site: http://maven.apache.org/plugins/maven-release-plugin-2.2.2/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -Stephen Note: * Beware the Sync... if you don't know how to setup proxies, you may have to wait up to 24h to see the staged site - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Release Plugin version 2.2.2
+1 Hervé Le Mardi 13 Décembre 2011 17:20:52 Stephen Connolly a écrit : Hi, We solved 5 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=H tmlversion=18224 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11144sta tus=1 Staging repo: https://repository.apache.org/content/repositories/maven-326/ Staging site: http://maven.apache.org/plugins/maven-release-plugin-2.2.2/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -Stephen Note: * Beware the Sync... if you don't know how to setup proxies, you may have to wait up to 24h to see the staged site - 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: [VOTE] Release Maven Release Plugin version 2.2.2
This vote has passed: +1 (binding): Stephen Connolly, Olivier Lamy, Hervé Boutemy +1 (non-binding): Tony Chemit +0: -1: I will now proceed with the rest of the release process. -Stephen On 13 December 2011 17:20, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Hi, We solved 5 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=18224 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11144status=1 Staging repo: https://repository.apache.org/content/repositories/maven-326/ Staging site: http://maven.apache.org/plugins/maven-release-plugin-2.2.2/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -Stephen Note: * Beware the Sync... if you don't know how to setup proxies, you may have to wait up to 24h to see the staged site - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Maven Release Plugin 2.2.2 Released
The Maven team is pleased to announce the release of the Maven XXX Plugin, version Y.Z This plugin is used to release a project with Maven, saving a lot of repetitive, manual work. Releasing a project is made in two steps: prepare and perform. http://maven.apache.org/plugins/maven-release-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version2.2.2/version /plugin Release Notes - Maven 2.x Release Plugin - Version 2.2.2 ** Bug * [MRELEASE-354] - Versions defined in profiles are not updated * [MRELEASE-454] - The Release-Plugin does not rewrite dependencies in the DependencyManagement with scope import * [MRELEASE-577] - release:prepare does not pass argument --settings with current settings.xml to inner maven ** Improvement * [MRELEASE-708] - upgrade to last scm 1.6 to integrate new scm provider mks integrity ** New Feature * [MRELEASE-467] - Release preparation should update version of plugin dependencies Enjoy, -The Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [ANN] Maven Release Plugin 2.2.2 Released
On 17 December 2011 01:46, Stephen Connolly steph...@apache.org wrote: The Maven team is pleased to announce the release of the Maven XXX Plugin, version Y.Z X, Y Z? This plugin is used to release a project with Maven, saving a lot of repetitive, manual work. Releasing a project is made in two steps: prepare and perform. http://maven.apache.org/plugins/maven-release-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version2.2.2/version /plugin Release Notes - Maven 2.x Release Plugin - Version 2.2.2 ** Bug * [MRELEASE-354] - Versions defined in profiles are not updated * [MRELEASE-454] - The Release-Plugin does not rewrite dependencies in the DependencyManagement with scope import * [MRELEASE-577] - release:prepare does not pass argument --settings with current settings.xml to inner maven ** Improvement * [MRELEASE-708] - upgrade to last scm 1.6 to integrate new scm provider mks integrity ** New Feature * [MRELEASE-467] - Release preparation should update version of plugin dependencies Enjoy, -The Maven team - 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: [ANN] Maven Release Plugin 2.2.2 Released
That should have been: The Maven team is pleased to announce the release of the Maven 2.x Release Plugin, version 2.2.2 Wayne On 12/16/11, sebb seb...@gmail.com wrote: On 17 December 2011 01:46, Stephen Connolly steph...@apache.org wrote: The Maven team is pleased to announce the release of the Maven XXX Plugin, version Y.Z X, Y Z? This plugin is used to release a project with Maven, saving a lot of repetitive, manual work. Releasing a project is made in two steps: prepare and perform. http://maven.apache.org/plugins/maven-release-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version2.2.2/version /plugin Release Notes - Maven 2.x Release Plugin - Version 2.2.2 ** Bug * [MRELEASE-354] - Versions defined in profiles are not updated * [MRELEASE-454] - The Release-Plugin does not rewrite dependencies in the DependencyManagement with scope import * [MRELEASE-577] - release:prepare does not pass argument --settings with current settings.xml to inner maven ** Improvement * [MRELEASE-708] - upgrade to last scm 1.6 to integrate new scm provider mks integrity ** New Feature * [MRELEASE-467] - Release preparation should update version of plugin dependencies Enjoy, -The Maven team - 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] Release Maven Release Plugin version 2.2.2
Hi, We solved 5 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=18224 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11144status=1 Staging repo: https://repository.apache.org/content/repositories/maven-326/ Staging site: http://maven.apache.org/plugins/maven-release-plugin-2.2.2/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -Stephen Note: * Beware the Sync... if you don't know how to setup proxies, you may have to wait up to 24h to see the staged site - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Release Plugin version 2.2.2
hmm some strangeness with site:stage-deploy but the content can be found if you dig down ;-) +1 from me btw - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 13 Dec 2011 17:20, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Hi, We solved 5 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=18224 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11144status=1 Staging repo: https://repository.apache.org/content/repositories/maven-326/ Staging site: http://maven.apache.org/plugins/maven-release-plugin-2.2.2/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -Stephen Note: * Beware the Sync... if you don't know how to setup proxies, you may have to wait up to 24h to see the staged site
Maven release plugin not honoring -Darguments
Is it a known issue that the release plugin does not honor the -Darguments? Specifically, I'm attempting to: mvn release:prepare -DdryRun=true -Darguments=-DskipTests=true -DfailIfNoTests=false It takes 40 minutes to get through a dryRun with tests on. We still have several kinks in the build to work out before the release plugin will work, so obviously running with tests on every dryRun is just making a hard task impossible. maven 3.0.3, apache-10 parent pom, maven-release-plugin 2.1 -David - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven release plugin not honoring -Darguments
IIRC you have to include your forked maven arguments in the release plugin configuration under arguments-DskipTests=true -DfailIfNoTests=false/arguments Perhaps someone else can say _why_ the m-r-p is set up so you can't set this on the command line? thanks david jencks On Sep 27, 2011, at 5:40 AM, David Blevins wrote: Is it a known issue that the release plugin does not honor the -Darguments? Specifically, I'm attempting to: mvn release:prepare -DdryRun=true -Darguments=-DskipTests=true -DfailIfNoTests=false It takes 40 minutes to get through a dryRun with tests on. We still have several kinks in the build to work out before the release plugin will work, so obviously running with tests on every dryRun is just making a hard task impossible. maven 3.0.3, apache-10 parent pom, maven-release-plugin 2.1 -David - 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: Maven release plugin not honoring -Darguments
you can if you understand shell escaping. - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 27 Sep 2011 17:58, David Jencks david_jen...@yahoo.com wrote: IIRC you have to include your forked maven arguments in the release plugin configuration under arguments-DskipTests=true -DfailIfNoTests=false/arguments Perhaps someone else can say _why_ the m-r-p is set up so you can't set this on the command line? thanks david jencks On Sep 27, 2011, at 5:40 AM, David Blevins wrote: Is it a known issue that the release plugin does not honor the -Darguments? Specifically, I'm attempting to: mvn release:prepare -DdryRun=true -Darguments=-DskipTests=true -DfailIfNoTests=false It takes 40 minutes to get through a dryRun with tests on. We still have several kinks in the build to work out before the release plugin will work, so obviously running with tests on every dryRun is just making a hard task impossible. maven 3.0.3, apache-10 parent pom, maven-release-plugin 2.1 -David - 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: Maven release plugin not honoring -Darguments
That's not it, the quoting was fine. Even with a single argument with no
spaces to -Darguments it still does not work.
Did some more digging and it seems the issue is in the apache-10 parent pom.
If you alter it like so, the arguments are passed as expected:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
version2.1/version
configuration
useReleaseProfilefalse/useReleaseProfile
goalsdeploy/goals
!--arguments-Papache-release/arguments--
arguments-Papache-release ${arguments}/arguments
/configuration
/plugin
Seems this is just a mistake as the full config as reported via -X contains
quite a bit of foo${foo}/foo style declarations. We likely just missed it
here.
Going to use a hacked parent pom for the moment but it would be great if we
could get an apache-11 pom out soonish.
-David
On Sep 27, 2011, at 10:54 AM, Stephen Connolly wrote:
you can if you understand shell escaping.
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 27 Sep 2011 17:58, David Jencks david_jen...@yahoo.com wrote:
IIRC you have to include your forked maven arguments in the release plugin
configuration under
arguments-DskipTests=true -DfailIfNoTests=false/arguments
Perhaps someone else can say _why_ the m-r-p is set up so you can't set
this on the command line?
thanks
david jencks
On Sep 27, 2011, at 5:40 AM, David Blevins wrote:
Is it a known issue that the release plugin does not honor the
-Darguments?
Specifically, I'm attempting to:
mvn release:prepare -DdryRun=true -Darguments=-DskipTests=true
-DfailIfNoTests=false
It takes 40 minutes to get through a dryRun with tests on. We still have
several kinks in the build to work out before the release plugin will work,
so obviously running with tests on every dryRun is just making a hard task
impossible.
maven 3.0.3, apache-10 parent pom, maven-release-plugin 2.1
-David
-
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
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Submitting patches to Maven release plugin
Hi We are making some enhancements to maven release plugin and maven release manager projects. What is the procedure to submit patches and enhancements? Thanks Nambi
Re: Submitting patches to Maven release plugin
Great! Patches into http://jira.codehaus.org/browse/MRELEASE is best. Regards, Brett On 08/09/2011, at 3:38 AM, Sankaran, Nambi wrote: Hi We are making some enhancements to maven release plugin and maven release manager projects. What is the procedure to submit patches and enhancements? Thanks Nambi -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Release plugin version 2.2.1
+1 from me bringing us to 3 binding votes On 28 July 2011 15:56, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Hi, This is a patch release to fix a particularly nasty regression: http://jira.codehaus.org/browse/MRELEASE-697 We solved 3 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=17502 Staging repo: https://repository.apache.org/content/repositories/maven-009/ Source distribution: https://repository.apache.org/content/repositories/maven-009/org/apache/maven/release/maven-release/2.2.1/maven-release-2.2.1-source-release.zip SCM tag: http://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.2.1 Staging site: http://maven.apache.org/plugins/maven-release-plugin-2.2.1/ http://maven.apache.org/maven-release/staging/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Guide to previewing site content ahead of the sync: http://www.apache.org/dev/project-site.html (and search on the page for HTTP proxy) Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, -Stephen - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[RESULT] [VOTE] Release Maven Release plugin version 2.2.1
Hi, The vote has passed with the following result: +1 (binding): Stephen Connolly, John Casey, Mark Struberg +1 (non-binding): Lukas Theussl, Mark Derricutt, Baptiste Mathus I will promote the artifacts to the central repo. -Stephen On 28 July 2011 15:56, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Hi, This is a patch release to fix a particularly nasty regression: http://jira.codehaus.org/browse/MRELEASE-697 We solved 3 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=17502 Staging repo: https://repository.apache.org/content/repositories/maven-009/ Source distribution: https://repository.apache.org/content/repositories/maven-009/org/apache/maven/release/maven-release/2.2.1/maven-release-2.2.1-source-release.zip SCM tag: http://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.2.1 Staging site: http://maven.apache.org/plugins/maven-release-plugin-2.2.1/ http://maven.apache.org/maven-release/staging/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Guide to previewing site content ahead of the sync: http://www.apache.org/dev/project-site.html (and search on the page for HTTP proxy) Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, -Stephen - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Maven Release Plugin 2.2.1 Released
The Maven team is pleased to announce the release of the Maven Release Plugin, version 2.2.1. This plugin is used to release a project with Maven, saving a lot of repetitive, manual work. Releasing a project is made in two steps: prepare and perform. http://maven.apache.org/plugins/maven-release-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version2.2.1/version /plugin Release Notes - Maven 2.x Release Plugin - Version 2.2.1 ** Bug * [MRELEASE-697] - version 2.2 includes SNAPSHOT in default tag name ** Improvement * [MRELEASE-239] - release:perform and release:prepare should accept multi-line goals/preparationGoals configurations * [MRELEASE-499] - Add to FAQ: prepare fails because of inheriting parent scm Enjoy, -The Maven Team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Release plugin version 2.2.1
A bit late, it might arrive after the mail of the release, but anyway: +1 for me too, just tested it on our main multimodule project. Thanks for the work, Stephen. 2011/7/29 Lukas Theussl ltheu...@apache.org +1 -Lukas On 07/28/2011 04:56 PM, Stephen Connolly wrote: Hi, This is a patch release to fix a particularly nasty regression: http://jira.codehaus.org/**browse/MRELEASE-697http://jira.codehaus.org/browse/MRELEASE-697 We solved 3 issues: http://jira.codehaus.org/**secure/ReleaseNote.jspa?** projectId=11144styleName=**Htmlversion=17502http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=17502 Staging repo: https://repository.apache.org/**content/repositories/maven-**009/https://repository.apache.org/content/repositories/maven-009/ Source distribution: https://repository.apache.org/**content/repositories/maven-** 009/org/apache/maven/release/**maven-release/2.2.1/maven-** release-2.2.1-source-release.**ziphttps://repository.apache.org/content/repositories/maven-009/org/apache/maven/release/maven-release/2.2.1/maven-release-2.2.1-source-release.zip SCM tag: http://svn.apache.org/repos/**asf/maven/release/tags/maven-** release-2.2.1http://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.2.1 Staging site: http://maven.apache.org/**plugins/maven-release-plugin-**2.2.1/http://maven.apache.org/plugins/maven-release-plugin-2.2.1/ http://maven.apache.org/maven-**release/staging/http://maven.apache.org/maven-release/staging/ Guide to testing staged releases: http://maven.apache.org/**guides/development/guide-** testing-releases.htmlhttp://maven.apache.org/guides/development/guide-testing-releases.html Guide to previewing site content ahead of the sync: http://www.apache.org/dev/**project-site.htmlhttp://www.apache.org/dev/project-site.html(and search on the page for HTTP proxy) Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, -Stephen --**--**- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org --**--**- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: [VOTE] Release Maven Release plugin version 2.2.1
+1 -Lukas On 07/28/2011 04:56 PM, Stephen Connolly wrote: Hi, This is a patch release to fix a particularly nasty regression: http://jira.codehaus.org/browse/MRELEASE-697 We solved 3 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=17502 Staging repo: https://repository.apache.org/content/repositories/maven-009/ Source distribution: https://repository.apache.org/content/repositories/maven-009/org/apache/maven/release/maven-release/2.2.1/maven-release-2.2.1-source-release.zip SCM tag: http://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.2.1 Staging site: http://maven.apache.org/plugins/maven-release-plugin-2.2.1/ http://maven.apache.org/maven-release/staging/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Guide to previewing site content ahead of the sync: http://www.apache.org/dev/project-site.html (and search on the page for HTTP proxy) Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, -Stephen - 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
Do we want to push a Maven Release Plugin 2.2.1 to include MRELEASE-697?
Since it is a rather nasty bug due to a typo on my behalf, do we push a release (2.2.1) now to include the fix and push all the unfixed issues back to 2.3 (where they currently live) -Stephen
Re: Do we want to push a Maven Release Plugin 2.2.1 to include MRELEASE-697?
If you are volunteering on the build, then +1 :) LieGrue, strub --- On Thu, 7/28/11, Stephen Connolly stephen.alan.conno...@gmail.com wrote: From: Stephen Connolly stephen.alan.conno...@gmail.com Subject: Do we want to push a Maven Release Plugin 2.2.1 to include MRELEASE-697? To: Maven Developers List dev@maven.apache.org Date: Thursday, July 28, 2011, 2:21 PM Since it is a rather nasty bug due to a typo on my behalf, do we push a release (2.2.1) now to include the fix and push all the unfixed issues back to 2.3 (where they currently live) -Stephen - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Do we want to push a Maven Release Plugin 2.2.1 to include MRELEASE-697?
well it was my typo in the first place, so yeah I'm willing to RM it... feck it... i'll do it On 28 July 2011 15:26, Mark Struberg strub...@yahoo.de wrote: If you are volunteering on the build, then +1 :) LieGrue, strub --- On Thu, 7/28/11, Stephen Connolly stephen.alan.conno...@gmail.com wrote: From: Stephen Connolly stephen.alan.conno...@gmail.com Subject: Do we want to push a Maven Release Plugin 2.2.1 to include MRELEASE-697? To: Maven Developers List dev@maven.apache.org Date: Thursday, July 28, 2011, 2:21 PM Since it is a rather nasty bug due to a typo on my behalf, do we push a release (2.2.1) now to include the fix and push all the unfixed issues back to 2.3 (where they currently live) -Stephen - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Do we want to push a Maven Release Plugin 2.2.1 to include MRELEASE-697?
+1 for a 2.2.1 Thanks - Mail original - De : Stephen Connolly stephen.alan.conno...@gmail.com À : Maven Developers List dev@maven.apache.org Cc : Envoyé le : Jeudi 28 Juillet 2011 16h28 Objet : Re: Do we want to push a Maven Release Plugin 2.2.1 to include MRELEASE-697? well it was my typo in the first place, so yeah I'm willing to RM it... feck it... i'll do it On 28 July 2011 15:26, Mark Struberg strub...@yahoo.de wrote: If you are volunteering on the build, then +1 :) LieGrue, strub --- On Thu, 7/28/11, Stephen Connolly stephen.alan.conno...@gmail.com wrote: From: Stephen Connolly stephen.alan.conno...@gmail.com Subject: Do we want to push a Maven Release Plugin 2.2.1 to include MRELEASE-697? To: Maven Developers List dev@maven.apache.org Date: Thursday, July 28, 2011, 2:21 PM Since it is a rather nasty bug due to a typo on my behalf, do we push a release (2.2.1) now to include the fix and push all the unfixed issues back to 2.3 (where they currently live) -Stephen - 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
[VOTE] Release Maven Release plugin version 2.2.1
Hi, This is a patch release to fix a particularly nasty regression: http://jira.codehaus.org/browse/MRELEASE-697 We solved 3 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=17502 Staging repo: https://repository.apache.org/content/repositories/maven-009/ Source distribution: https://repository.apache.org/content/repositories/maven-009/org/apache/maven/release/maven-release/2.2.1/maven-release-2.2.1-source-release.zip SCM tag: http://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.2.1 Staging site: http://maven.apache.org/plugins/maven-release-plugin-2.2.1/ http://maven.apache.org/maven-release/staging/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Guide to previewing site content ahead of the sync: http://www.apache.org/dev/project-site.html (and search on the page for HTTP proxy) Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, -Stephen - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Release plugin version 2.2.1
+1 On 7/28/11 10:56 AM, Stephen Connolly wrote: Hi, This is a patch release to fix a particularly nasty regression: http://jira.codehaus.org/browse/MRELEASE-697 We solved 3 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=17502 Staging repo: https://repository.apache.org/content/repositories/maven-009/ Source distribution: https://repository.apache.org/content/repositories/maven-009/org/apache/maven/release/maven-release/2.2.1/maven-release-2.2.1-source-release.zip SCM tag: http://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.2.1 Staging site: http://maven.apache.org/plugins/maven-release-plugin-2.2.1/ http://maven.apache.org/maven-release/staging/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Guide to previewing site content ahead of the sync: http://www.apache.org/dev/project-site.html (and search on the page for HTTP proxy) Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, -Stephen - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- John Casey Developer, PMC Chair - Apache Maven (http://maven.apache.org) Blog: http://www.johnofalltrades.name/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Release plugin version 2.2.1
+1 source looks ok, signing looks ok, did a quick run on my test project - also ok. LieGrue, strub --- On Thu, 7/28/11, Stephen Connolly stephen.alan.conno...@gmail.com wrote: From: Stephen Connolly stephen.alan.conno...@gmail.com Subject: [VOTE] Release Maven Release plugin version 2.2.1 To: Maven Developers List dev@maven.apache.org Date: Thursday, July 28, 2011, 2:56 PM Hi, This is a patch release to fix a particularly nasty regression: http://jira.codehaus.org/browse/MRELEASE-697 We solved 3 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=17502 Staging repo: https://repository.apache.org/content/repositories/maven-009/ Source distribution: https://repository.apache.org/content/repositories/maven-009/org/apache/maven/release/maven-release/2.2.1/maven-release-2.2.1-source-release.zip SCM tag: http://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.2.1 Staging site: http://maven.apache.org/plugins/maven-release-plugin-2.2.1/ http://maven.apache.org/maven-release/staging/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Guide to previewing site content ahead of the sync: http://www.apache.org/dev/project-site.html (and search on the page for HTTP proxy) Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, -Stephen - 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: Do we want to push a Maven Release Plugin 2.2.1 to include MRELEASE-697?
+1 Le 28 juil. 2011 à 16:49, Julien HENRY henr...@yahoo.fr a écrit : +1 for a 2.2.1 Thanks - Mail original - De : Stephen Connolly stephen.alan.conno...@gmail.com À : Maven Developers List dev@maven.apache.org Cc : Envoyé le : Jeudi 28 Juillet 2011 16h28 Objet : Re: Do we want to push a Maven Release Plugin 2.2.1 to include MRELEASE-697? well it was my typo in the first place, so yeah I'm willing to RM it... feck it... i'll do it On 28 July 2011 15:26, Mark Struberg strub...@yahoo.de wrote: If you are volunteering on the build, then +1 :) LieGrue, strub --- On Thu, 7/28/11, Stephen Connolly stephen.alan.conno...@gmail.com wrote: From: Stephen Connolly stephen.alan.conno...@gmail.com Subject: Do we want to push a Maven Release Plugin 2.2.1 to include MRELEASE-697? To: Maven Developers List dev@maven.apache.org Date: Thursday, July 28, 2011, 2:21 PM Since it is a rather nasty bug due to a typo on my behalf, do we push a release (2.2.1) now to include the fix and push all the unfixed issues back to 2.3 (where they currently live) -Stephen - 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Do we want to push a Maven Release Plugin 2.2.1 to include MRELEASE-697?
he he. vote already in progress ;-) - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 28 Jul 2011 18:41, Arnaud Héritier aherit...@gmail.com wrote: +1 Le 28 juil. 2011 à 16:49, Julien HENRY henr...@yahoo.fr a écrit : +1 for a 2.2.1 Thanks - Mail original - De : Stephen Connolly stephen.alan.conno...@gmail.com À : Maven Developers List dev@maven.apache.org Cc : Envoyé le : Jeudi 28 Juillet 2011 16h28 Objet : Re: Do we want to push a Maven Release Plugin 2.2.1 to include MRELEASE-697? well it was my typo in the first place, so yeah I'm willing to RM it... feck it... i'll do it On 28 July 2011 15:26, Mark Struberg strub...@yahoo.de wrote: If you are volunteering on the build, then +1 :) LieGrue, strub --- On Thu, 7/28/11, Stephen Connolly stephen.alan.conno...@gmail.com wrote: From: Stephen Connolly stephen.alan.conno...@gmail.com Subject: Do we want to push a Maven Release Plugin 2.2.1 to include MRELEASE-697? To: Maven Developers List dev@maven.apache.org Date: Thursday, July 28, 2011, 2:21 PM Since it is a rather nasty bug due to a typo on my behalf, do we push a release (2.2.1) now to include the fix and push all the unfixed issues back to 2.3 (where they currently live) -Stephen - 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Release plugin version 2.2.1
+1 Non Binding On 29/07/2011, at 2:56 AM, Stephen Connolly wrote: Hi, This is a patch release to fix a particularly nasty regression: http://jira.codehaus.org/browse/MRELEASE-697 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Maven Release Plugin 2.2 Released
The Maven team is pleased to announce the release of the Maven Release Plugin, version 2.2 This plugin is used to release a project with Maven, saving a lot of repetitive, manual work. Releasing a project is made in two steps: prepare and perform. http://maven.apache.org/plugins/maven-release-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version2.2/version /plugin Release Notes - Maven 2.x Release Plugin - Version 2.2 ** Bug * [MRELEASE-374] - Snapshot versions unusable in batch mode * [MRELEASE-622] - Creating label fails for ClearCase with message 'Unable to determine VOB for pathname ..' * [MRELEASE-661] - Exception: String index out of range: -1 ** Improvement * [MRELEASE-591] - release:update-versions: add option to do a checkin * [MRELEASE-605] - when not pushing changes to remote git repo in 2.1, the release plugin fails on release:perform * [MRELEASE-628] - Subversion --trust-server-cert option * [MRELEASE-641] - upgrade to scm 1.5 (hg plugin insists on 'pushing') ** New Feature * [MRELEASE-159] - Support a pattern to generate the release tag * [MRELEASE-457] - Non sparse-checkout SCM support * [MRELEASE-613] - Add a parameter that tells the plugin to wait for X seconds before tagging * [MRELEASE-621] - Add a postPrepareGoals * [MRELEASE-648] - Putting SVN password in settings.xml doesn't support password encryption Enjoy, -The Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Request to release maven-release-plugin 2.2
Hi Stephen! I've fixed the tests now. I'll now go on and try to fix the localCheckout with GIT in submodules. LieGrue, strub --- On Sat, 6/25/11, Stephen Connolly stephen.alan.conno...@gmail.com wrote: From: Stephen Connolly stephen.alan.conno...@gmail.com Subject: Re: Request to release maven-release-plugin 2.2 To: Maven Developers List dev@maven.apache.org Date: Saturday, June 25, 2011, 12:59 PM i can take a shot. but it will be Monday before i have the bandwidth. - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 25 Jun 2011 12:40, Mark Struberg strub...@yahoo.de wrote: kk I'll do it this evening. But first someone needs to fix the broken unit tests (mockReleaseManager missing) ;) Someone working on that already? LieGrue, strub --- On Sat, 6/25/11, Stephen Connolly stephen.alan.conno...@gmail.com wrote: From: Stephen Connolly stephen.alan.conno...@gmail.com Subject: Re: Request to release maven-release-plugin 2.2 To: Maven Developers List dev@maven.apache.org Date: Saturday, June 25, 2011, 11:37 AM i can give you until noon gmt+1 Tuesday... at that point i need to cut something - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 25 Jun 2011 11:32, Mark Struberg strub...@yahoo.de wrote: Hi! If you'd give me a day (after fixing the broken tests), then I'd like to resolve the problem that a release from a sparse directory in GIT doesn't work if localCheckout is used. The reason is pretty simple: I currently construct the local checkout url as file:// + releaseDescriptor.getWorkingDirectory(). Guess we need to put the 'base directory' of the SCM repository ReleaseDescriptor somehow. Of course, that's not really a blocker issue because by not using localCheckout all things work fine. LieGrue, strub --- On Sat, 6/25/11, Dan Tran dant...@gmail.com wrote: From: Dan Tran dant...@gmail.com Subject: Re: Request to release maven-release-plugin 2.2 To: Maven Developers List dev@maven.apache.org Date: Saturday, June 25, 2011, 3:32 AM Why not just cut with what we currently have? :-) I will do my best to review -D On Fri, Jun 24, 2011 at 1:51 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: hervé has been making some tweak today (as have i) if nobody steps up, i should be able to kick off a release on Monday. won't have the bandwidth before then, and there are a couple of critical issues in jira... be good to do a bug scrub first. Dan, if you can review the open critical issues and feed back your feeling on which can be downgraded i'll drive the release. Deal? - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 24 Jun 2011 16:42, Dan Tran dant...@gmail.com wrote: Hi Can we have a new release for this plugin? I am anxious to pick up http://jira.codehaus.org/browse/MRELEASE-648 -D - 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 - 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Request to release maven-release-plugin 2.2
cool - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 26 Jun 2011 18:40, Mark Struberg strub...@yahoo.de wrote: Hi Stephen! I've fixed the tests now. I'll now go on and try to fix the localCheckout with GIT in submodules. LieGrue, strub --- On Sat, 6/25/11, Stephen Connolly stephen.alan.conno...@gmail.com wrote: From: Stephen Connolly stephen.alan.conno...@gmail.com Subject: Re: Request to release maven-release-plugin 2.2 To: Maven Developers List dev@maven.apache.org Date: Saturday, June 25, 2011, 12:59 PM i can take a shot. but it will be Monday before i have the bandwidth. - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 25 Jun 2011 12:40, Mark Struberg strub...@yahoo.de wrote: kk I'll do it this evening. But first someone needs to fix the broken unit tests (mockReleaseManager missing) ;) Someone working on that already? LieGrue, strub --- On Sat, 6/25/11, Stephen Connolly stephen.alan.conno...@gmail.com wrote: From: Stephen Connolly stephen.alan.conno...@gmail.com Subject: Re: Request to release maven-release-plugin 2.2 To: Maven Developers List dev@maven.apache.org Date: Saturday, June 25, 2011, 11:37 AM i can give you until noon gmt+1 Tuesday... at that point i need to cut something - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 25 Jun 2011 11:32, Mark Struberg strub...@yahoo.de wrote: Hi! If you'd give me a day (after fixing the broken tests), then I'd like to resolve the problem that a release from a sparse directory in GIT doesn't work if localCheckout is used. The reason is pretty simple: I currently construct the local checkout url as file:// + releaseDescriptor.getWorkingDirectory(). Guess we need to put the 'base directory' of the SCM repository ReleaseDescriptor somehow. Of course, that's not really a blocker issue because by not using localCheckout all things work fine. LieGrue, strub --- On Sat, 6/25/11, Dan Tran dant...@gmail.com wrote: From: Dan Tran dant...@gmail.com Subject: Re: Request to release maven-release-plugin 2.2 To: Maven Developers List dev@maven.apache.org Date: Saturday, June 25, 2011, 3:32 AM Why not just cut with what we currently have? :-) I will do my best to review -D On Fri, Jun 24, 2011 at 1:51 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: hervé has been making some tweak today (as have i) if nobody steps up, i should be able to kick off a release on Monday. won't have the bandwidth before then, and there are a couple of critical issues in jira... be good to do a bug scrub first. Dan, if you can review the open critical issues and feed back your feeling on which can be downgraded i'll drive the release. Deal? - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 24 Jun 2011 16:42, Dan Tran dant...@gmail.com wrote: Hi Can we have a new release for this plugin? I am anxious to pick up http://jira.codehaus.org/browse/MRELEASE-648 -D - 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 - 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Request to release maven-release-plugin 2.2
Stephen, please feel free to go on with the release. For fixing the sparse scenario with localCheckout, I'd need to first add the relativePathProjectDirectory info to maven-scm-provider-gitexe. Afterwards I can parse this info and correctly use it for constructing the local file:// clone URL. But that will need a bit (+ a fresh maven-scm release) LieGrue, strub --- On Sun, 6/26/11, Stephen Connolly stephen.alan.conno...@gmail.com wrote: From: Stephen Connolly stephen.alan.conno...@gmail.com Subject: Re: Request to release maven-release-plugin 2.2 To: Maven Developers List dev@maven.apache.org Date: Sunday, June 26, 2011, 7:30 PM cool - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 26 Jun 2011 18:40, Mark Struberg strub...@yahoo.de wrote: Hi Stephen! I've fixed the tests now. I'll now go on and try to fix the localCheckout with GIT in submodules. LieGrue, strub --- On Sat, 6/25/11, Stephen Connolly stephen.alan.conno...@gmail.com wrote: From: Stephen Connolly stephen.alan.conno...@gmail.com Subject: Re: Request to release maven-release-plugin 2.2 To: Maven Developers List dev@maven.apache.org Date: Saturday, June 25, 2011, 12:59 PM i can take a shot. but it will be Monday before i have the bandwidth. - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 25 Jun 2011 12:40, Mark Struberg strub...@yahoo.de wrote: kk I'll do it this evening. But first someone needs to fix the broken unit tests (mockReleaseManager missing) ;) Someone working on that already? LieGrue, strub --- On Sat, 6/25/11, Stephen Connolly stephen.alan.conno...@gmail.com wrote: From: Stephen Connolly stephen.alan.conno...@gmail.com Subject: Re: Request to release maven-release-plugin 2.2 To: Maven Developers List dev@maven.apache.org Date: Saturday, June 25, 2011, 11:37 AM i can give you until noon gmt+1 Tuesday... at that point i need to cut something - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 25 Jun 2011 11:32, Mark Struberg strub...@yahoo.de wrote: Hi! If you'd give me a day (after fixing the broken tests), then I'd like to resolve the problem that a release from a sparse directory in GIT doesn't work if localCheckout is used. The reason is pretty simple: I currently construct the local checkout url as file:// + releaseDescriptor.getWorkingDirectory(). Guess we need to put the 'base directory' of the SCM repository ReleaseDescriptor somehow. Of course, that's not really a blocker issue because by not using localCheckout all things work fine. LieGrue, strub --- On Sat, 6/25/11, Dan Tran dant...@gmail.com wrote: From: Dan Tran dant...@gmail.com Subject: Re: Request to release maven-release-plugin 2.2 To: Maven Developers List dev@maven.apache.org Date: Saturday, June 25, 2011, 3:32 AM Why not just cut with what we currently have? :-) I will do my best to review -D On Fri, Jun 24, 2011 at 1:51 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: hervé has been making some tweak today (as have i) if nobody steps up, i should be able to kick off a release on Monday. won't have the bandwidth before then, and there are a couple of critical issues in jira... be good to do a bug scrub first. Dan, if you can review the open critical issues and feed back your feeling on which can be downgraded i'll drive the release. Deal? - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 24 Jun 2011 16:42, Dan Tran dant...@gmail.com wrote: Hi Can we have a new release for this plugin? I am anxious to pick up http://jira.codehaus.org/browse/MRELEASE-648 -D - 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: Request to release maven-release-plugin 2.2
well i'll take a dig through jira then and see if there is anything low hanging, otherwise i'll push something tomorrow - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 26 Jun 2011 22:26, Mark Struberg strub...@yahoo.de wrote: Stephen, please feel free to go on with the release. For fixing the sparse scenario with localCheckout, I'd need to first add the relativePathProjectDirectory info to maven-scm-provider-gitexe. Afterwards I can parse this info and correctly use it for constructing the local file:// clone URL. But that will need a bit (+ a fresh maven-scm release) LieGrue, strub --- On Sun, 6/26/11, Stephen Connolly stephen.alan.conno...@gmail.com wrote: From: Stephen Connolly stephen.alan.conno...@gmail.com Subject: Re: Request to release maven-release-plugin 2.2 To: Maven Developers List dev@maven.apache.org Date: Sunday, June 26, 2011, 7:30 PM cool - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 26 Jun 2011 18:40, Mark Struberg strub...@yahoo.de wrote: Hi Stephen! I've fixed the tests now. I'll now go on and try to fix the localCheckout with GIT in submodules. LieGrue, strub --- On Sat, 6/25/11, Stephen Connolly stephen.alan.conno...@gmail.com wrote: From: Stephen Connolly stephen.alan.conno...@gmail.com Subject: Re: Request to release maven-release-plugin 2.2 To: Maven Developers List dev@maven.apache.org Date: Saturday, June 25, 2011, 12:59 PM i can take a shot. but it will be Monday before i have the bandwidth. - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 25 Jun 2011 12:40, Mark Struberg strub...@yahoo.de wrote: kk I'll do it this evening. But first someone needs to fix the broken unit tests (mockReleaseManager missing) ;) Someone working on that already? LieGrue, strub --- On Sat, 6/25/11, Stephen Connolly stephen.alan.conno...@gmail.com wrote: From: Stephen Connolly stephen.alan.conno...@gmail.com Subject: Re: Request to release maven-release-plugin 2.2 To: Maven Developers List dev@maven.apache.org Date: Saturday, June 25, 2011, 11:37 AM i can give you until noon gmt+1 Tuesday... at that point i need to cut something - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 25 Jun 2011 11:32, Mark Struberg strub...@yahoo.de wrote: Hi! If you'd give me a day (after fixing the broken tests), then I'd like to resolve the problem that a release from a sparse directory in GIT doesn't work if localCheckout is used. The reason is pretty simple: I currently construct the local checkout url as file:// + releaseDescriptor.getWorkingDirectory(). Guess we need to put the 'base directory' of the SCM repository ReleaseDescriptor somehow. Of course, that's not really a blocker issue because by not using localCheckout all things work fine. LieGrue, strub --- On Sat, 6/25/11, Dan Tran dant...@gmail.com wrote: From: Dan Tran dant...@gmail.com Subject: Re: Request to release maven-release-plugin 2.2 To: Maven Developers List dev@maven.apache.org Date: Saturday, June 25, 2011, 3:32 AM Why not just cut with what we currently have? :-) I will do my best to review -D On Fri, Jun 24, 2011 at 1:51 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: hervé has been making some tweak today (as have i) if nobody steps up, i should be able to kick off a release on Monday. won't have the bandwidth before then, and there are a couple of critical issues in jira... be good to do a bug scrub first. Dan, if you can review the open critical issues and feed back your feeling on which can be downgraded i'll drive the release. Deal? - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 24 Jun 2011 16:42, Dan Tran dant...@gmail.com wrote: Hi Can we have a new release for this plugin? I am anxious to pick up http://jira.codehaus.org/browse/MRELEASE-648 -D - To unsubscribe, e-mail: dev-unsubscr
Re: Request to release maven-release-plugin 2.2
ok for me: I finished my modifications Regards, Hervé Le lundi 27 juin 2011, Stephen Connolly a écrit : well i'll take a dig through jira then and see if there is anything low hanging, otherwise i'll push something tomorrow - Stephen - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Request to release maven-release-plugin 2.2
Hi! If you'd give me a day (after fixing the broken tests), then I'd like to resolve the problem that a release from a sparse directory in GIT doesn't work if localCheckout is used. The reason is pretty simple: I currently construct the local checkout url as file:// + releaseDescriptor.getWorkingDirectory(). Guess we need to put the 'base directory' of the SCM repository ReleaseDescriptor somehow. Of course, that's not really a blocker issue because by not using localCheckout all things work fine. LieGrue, strub --- On Sat, 6/25/11, Dan Tran dant...@gmail.com wrote: From: Dan Tran dant...@gmail.com Subject: Re: Request to release maven-release-plugin 2.2 To: Maven Developers List dev@maven.apache.org Date: Saturday, June 25, 2011, 3:32 AM Why not just cut with what we currently have? :-) I will do my best to review -D On Fri, Jun 24, 2011 at 1:51 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: hervé has been making some tweak today (as have i) if nobody steps up, i should be able to kick off a release on Monday. won't have the bandwidth before then, and there are a couple of critical issues in jira... be good to do a bug scrub first. Dan, if you can review the open critical issues and feed back your feeling on which can be downgraded i'll drive the release. Deal? - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 24 Jun 2011 16:42, Dan Tran dant...@gmail.com wrote: Hi Can we have a new release for this plugin? I am anxious to pick up http://jira.codehaus.org/browse/MRELEASE-648 -D - 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Request to release maven-release-plugin 2.2
i can give you until noon gmt+1 Tuesday... at that point i need to cut something - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 25 Jun 2011 11:32, Mark Struberg strub...@yahoo.de wrote: Hi! If you'd give me a day (after fixing the broken tests), then I'd like to resolve the problem that a release from a sparse directory in GIT doesn't work if localCheckout is used. The reason is pretty simple: I currently construct the local checkout url as file:// + releaseDescriptor.getWorkingDirectory(). Guess we need to put the 'base directory' of the SCM repository ReleaseDescriptor somehow. Of course, that's not really a blocker issue because by not using localCheckout all things work fine. LieGrue, strub --- On Sat, 6/25/11, Dan Tran dant...@gmail.com wrote: From: Dan Tran dant...@gmail.com Subject: Re: Request to release maven-release-plugin 2.2 To: Maven Developers List dev@maven.apache.org Date: Saturday, June 25, 2011, 3:32 AM Why not just cut with what we currently have? :-) I will do my best to review -D On Fri, Jun 24, 2011 at 1:51 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: hervé has been making some tweak today (as have i) if nobody steps up, i should be able to kick off a release on Monday. won't have the bandwidth before then, and there are a couple of critical issues in jira... be good to do a bug scrub first. Dan, if you can review the open critical issues and feed back your feeling on which can be downgraded i'll drive the release. Deal? - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 24 Jun 2011 16:42, Dan Tran dant...@gmail.com wrote: Hi Can we have a new release for this plugin? I am anxious to pick up http://jira.codehaus.org/browse/MRELEASE-648 -D - 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Request to release maven-release-plugin 2.2
kk I'll do it this evening. But first someone needs to fix the broken unit tests (mockReleaseManager missing) ;) Someone working on that already? LieGrue, strub --- On Sat, 6/25/11, Stephen Connolly stephen.alan.conno...@gmail.com wrote: From: Stephen Connolly stephen.alan.conno...@gmail.com Subject: Re: Request to release maven-release-plugin 2.2 To: Maven Developers List dev@maven.apache.org Date: Saturday, June 25, 2011, 11:37 AM i can give you until noon gmt+1 Tuesday... at that point i need to cut something - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 25 Jun 2011 11:32, Mark Struberg strub...@yahoo.de wrote: Hi! If you'd give me a day (after fixing the broken tests), then I'd like to resolve the problem that a release from a sparse directory in GIT doesn't work if localCheckout is used. The reason is pretty simple: I currently construct the local checkout url as file:// + releaseDescriptor.getWorkingDirectory(). Guess we need to put the 'base directory' of the SCM repository ReleaseDescriptor somehow. Of course, that's not really a blocker issue because by not using localCheckout all things work fine. LieGrue, strub --- On Sat, 6/25/11, Dan Tran dant...@gmail.com wrote: From: Dan Tran dant...@gmail.com Subject: Re: Request to release maven-release-plugin 2.2 To: Maven Developers List dev@maven.apache.org Date: Saturday, June 25, 2011, 3:32 AM Why not just cut with what we currently have? :-) I will do my best to review -D On Fri, Jun 24, 2011 at 1:51 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: hervé has been making some tweak today (as have i) if nobody steps up, i should be able to kick off a release on Monday. won't have the bandwidth before then, and there are a couple of critical issues in jira... be good to do a bug scrub first. Dan, if you can review the open critical issues and feed back your feeling on which can be downgraded i'll drive the release. Deal? - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 24 Jun 2011 16:42, Dan Tran dant...@gmail.com wrote: Hi Can we have a new release for this plugin? I am anxious to pick up http://jira.codehaus.org/browse/MRELEASE-648 -D - 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 - 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: Request to release maven-release-plugin 2.2
(saw your call on IRC just a few minutes after you leave...) if someone explains me what is this mock about, I'm happy to learn and help but for the moment, I don't understand what has to be done Regards, Hervé Le samedi 25 juin 2011, Mark Struberg a écrit : kk I'll do it this evening. But first someone needs to fix the broken unit tests (mockReleaseManager missing) ;) Someone working on that already? LieGrue, strub --- On Sat, 6/25/11, Stephen Connolly stephen.alan.conno...@gmail.com wrote: From: Stephen Connolly stephen.alan.conno...@gmail.com Subject: Re: Request to release maven-release-plugin 2.2 To: Maven Developers List dev@maven.apache.org Date: Saturday, June 25, 2011, 11:37 AM i can give you until noon gmt+1 Tuesday... at that point i need to cut something - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 25 Jun 2011 11:32, Mark Struberg strub...@yahoo.de wrote: Hi! If you'd give me a day (after fixing the broken tests), then I'd like to resolve the problem that a release from a sparse directory in GIT doesn't work if localCheckout is used. The reason is pretty simple: I currently construct the local checkout url as file:// + releaseDescriptor.getWorkingDirectory(). Guess we need to put the 'base directory' of the SCM repository ReleaseDescriptor somehow. Of course, that's not really a blocker issue because by not using localCheckout all things work fine. LieGrue, strub --- On Sat, 6/25/11, Dan Tran dant...@gmail.com wrote: From: Dan Tran dant...@gmail.com Subject: Re: Request to release maven-release-plugin 2.2 To: Maven Developers List dev@maven.apache.org Date: Saturday, June 25, 2011, 3:32 AM Why not just cut with what we currently have? :-) I will do my best to review -D On Fri, Jun 24, 2011 at 1:51 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: hervé has been making some tweak today (as have i) if nobody steps up, i should be able to kick off a release on Monday. won't have the bandwidth before then, and there are a couple of critical issues in jira... be good to do a bug scrub first. Dan, if you can review the open critical issues and feed back your feeling on which can be downgraded i'll drive the release. Deal? - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 24 Jun 2011 16:42, Dan Tran dant...@gmail.com wrote: Hi Can we have a new release for this plugin? I am anxious to pick up http://jira.codehaus.org/browse/MRELEASE-648 -D - 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 - 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Request to release maven-release-plugin 2.2
i can take a shot. but it will be Monday before i have the bandwidth. - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 25 Jun 2011 12:40, Mark Struberg strub...@yahoo.de wrote: kk I'll do it this evening. But first someone needs to fix the broken unit tests (mockReleaseManager missing) ;) Someone working on that already? LieGrue, strub --- On Sat, 6/25/11, Stephen Connolly stephen.alan.conno...@gmail.com wrote: From: Stephen Connolly stephen.alan.conno...@gmail.com Subject: Re: Request to release maven-release-plugin 2.2 To: Maven Developers List dev@maven.apache.org Date: Saturday, June 25, 2011, 11:37 AM i can give you until noon gmt+1 Tuesday... at that point i need to cut something - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 25 Jun 2011 11:32, Mark Struberg strub...@yahoo.de wrote: Hi! If you'd give me a day (after fixing the broken tests), then I'd like to resolve the problem that a release from a sparse directory in GIT doesn't work if localCheckout is used. The reason is pretty simple: I currently construct the local checkout url as file:// + releaseDescriptor.getWorkingDirectory(). Guess we need to put the 'base directory' of the SCM repository ReleaseDescriptor somehow. Of course, that's not really a blocker issue because by not using localCheckout all things work fine. LieGrue, strub --- On Sat, 6/25/11, Dan Tran dant...@gmail.com wrote: From: Dan Tran dant...@gmail.com Subject: Re: Request to release maven-release-plugin 2.2 To: Maven Developers List dev@maven.apache.org Date: Saturday, June 25, 2011, 3:32 AM Why not just cut with what we currently have? :-) I will do my best to review -D On Fri, Jun 24, 2011 at 1:51 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: hervé has been making some tweak today (as have i) if nobody steps up, i should be able to kick off a release on Monday. won't have the bandwidth before then, and there are a couple of critical issues in jira... be good to do a bug scrub first. Dan, if you can review the open critical issues and feed back your feeling on which can be downgraded i'll drive the release. Deal? - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 24 Jun 2011 16:42, Dan Tran dant...@gmail.com wrote: Hi Can we have a new release for this plugin? I am anxious to pick up http://jira.codehaus.org/browse/MRELEASE-648 -D - 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 - 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
Request to release maven-release-plugin 2.2
Hi Can we have a new release for this plugin? I am anxious to pick up http://jira.codehaus.org/browse/MRELEASE-648 -D - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Request to release maven-release-plugin 2.2
hervé has been making some tweak today (as have i) if nobody steps up, i should be able to kick off a release on Monday. won't have the bandwidth before then, and there are a couple of critical issues in jira... be good to do a bug scrub first. Dan, if you can review the open critical issues and feed back your feeling on which can be downgraded i'll drive the release. Deal? - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 24 Jun 2011 16:42, Dan Tran dant...@gmail.com wrote: Hi Can we have a new release for this plugin? I am anxious to pick up http://jira.codehaus.org/browse/MRELEASE-648 -D - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Request to release maven-release-plugin 2.2
Why not just cut with what we currently have? :-) I will do my best to review -D On Fri, Jun 24, 2011 at 1:51 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: hervé has been making some tweak today (as have i) if nobody steps up, i should be able to kick off a release on Monday. won't have the bandwidth before then, and there are a couple of critical issues in jira... be good to do a bug scrub first. Dan, if you can review the open critical issues and feed back your feeling on which can be downgraded i'll drive the release. Deal? - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 24 Jun 2011 16:42, Dan Tran dant...@gmail.com wrote: Hi Can we have a new release for this plugin? I am anxious to pick up http://jira.codehaus.org/browse/MRELEASE-648 -D - 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
[RESULT] Release Maven Release plugin version 2.1
Binding +1 votes: Brett, Emmanuel, Olivier Non-binding +1 votes: Mark I'm proceeding with the release. Cheers, Brett On 04/10/2010, at 11:01 PM, Brett Porter wrote: Hi, We solved 17 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=12571 Staging repo: https://repository.apache.org/content/repositories/maven-002/ Source distribution: https://repository.apache.org/content/repositories/maven-002/org/apache/maven/release/maven-release/2.1/maven-release-2.1-source-release.zip SCM tag: http://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.1 Staging site: http://maven.apache.org/plugins/maven-release-plugin-2.1/ http://maven.apache.org/maven-release/staging/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Cheers, Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Maven Release Plugin 2.1 Released
The Maven team is pleased to announce the release of the Maven Release Plugin, version 2.1 This plugin is used to release a project with Maven, saving a lot of repetitive, manual work. Releasing a project is made in two steps: prepare and perform. http://maven.apache.org/plugins/maven-release-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version2.1/version /plugin Release Notes - Maven Release Plugin - Version 2.1 ** Bug * [MRELEASE-128] - SCM properties being replaced during release:perform * [MRELEASE-317] - release:prepare should fail if any pom depends on SNAPSHOT parent * [MRELEASE-318] - Release plugin throws NullPointerException when using version range for dependency * [MRELEASE-350] - Option '0' for specify the selection number ( 0:All 1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ): is broken * [MRELEASE-370] - release:prepare is not updating inter-modules dependencies to the next version snapshot identifier correctly (-DdryRun=true). * [MRELEASE-458] - Branch Does Not Honor updateWorkingCopyVersions Setting * [MRELEASE-524] - command line versions don't seem to work on release:branch for specific format * [MRELEASE-536] - CommonBasedir Calculation fails on windows * [MRELEASE-546] - regression introduced in MRELEASE-261 * [MRELEASE-551] - Unable to release with maven 3 when having no $HOME/.m2/settings.xml * [MRELEASE-563] - help strings need help, they are not helpful out of context * [MRELEASE-586] - release:perform - The temporary file pom.xml.branch should be ignored as pom.xml.next and pom.xml.tag are ignored * [MRELEASE-589] - Resolved dependencies overwritten when multiple subprojects with SNAPSHOT dependencies are released ** Improvement * [MRELEASE-497] - Don't overwrite SVN auth cache * [MRELEASE-530] - Git provider does 'git push' during 'mvn release:prepare' which causes unwanted problems (scm 1.4 upgrade) * [MRELEASE-554] - Allow custom files to be modified before doing a prepare or branch... * [MRELEASE-583] - Better Snapshot Dependency Handling Enjoy, -The Maven team -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Release plugin version 2.1
+1 Emmanuel On Mon, Oct 4, 2010 at 2:01 PM, Brett Porter br...@apache.org wrote: Hi, We solved 17 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=12571 Staging repo: https://repository.apache.org/content/repositories/maven-002/ Source distribution: https://repository.apache.org/content/repositories/maven-002/org/apache/maven/release/maven-release/2.1/maven-release-2.1-source-release.zip SCM tag: http://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.1 Staging site: http://maven.apache.org/plugins/maven-release-plugin-2.1/ http://maven.apache.org/maven-release/staging/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Cheers, Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Release plugin version 2.1
+1 (thanks for pushing this !) 2010/10/4 Brett Porter br...@apache.org: Hi, We solved 17 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=12571 Staging repo: https://repository.apache.org/content/repositories/maven-002/ Source distribution: https://repository.apache.org/content/repositories/maven-002/org/apache/maven/release/maven-release/2.1/maven-release-2.1-source-release.zip SCM tag: http://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.1 Staging site: http://maven.apache.org/plugins/maven-release-plugin-2.1/ http://maven.apache.org/maven-release/staging/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Cheers, Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier http://twitter.com/olamy http://www.linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Release plugin version 2.1
Hi Brett, Brett Porter wrote: Hi, We solved 17 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=12571 Staging repo: https://repository.apache.org/content/repositories/maven-002/ Source distribution: https://repository.apache.org/content/repositories/maven-002/org/apache/maven/release/maven- release/2.1/maven-release-2.1-source-release.zip SCM tag: http://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.1 Staging site: http://maven.apache.org/plugins/maven-release-plugin-2.1/ http://maven.apache.org/maven-release/staging/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Well, actually I am a bit dissapointed to see MRELEASE-159 shifted again. This issue is now open for more than 4 years, has 29 votes, and a current patch including tests. And I don't understand your last comment on this issue, Brett. Is that meant as a TODO for a Maven dev? - Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Release plugin version 2.1
On 06/10/2010, at 12:15 AM, Jörg Schaible wrote: Hi Brett, Brett Porter wrote: Hi, We solved 17 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=12571 Staging repo: https://repository.apache.org/content/repositories/maven-002/ Source distribution: https://repository.apache.org/content/repositories/maven-002/org/apache/maven/release/maven- release/2.1/maven-release-2.1-source-release.zip SCM tag: http://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.1 Staging site: http://maven.apache.org/plugins/maven-release-plugin-2.1/ http://maven.apache.org/maven-release/staging/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Well, actually I am a bit dissapointed to see MRELEASE-159 shifted again. This issue is now open for more than 4 years, has 29 votes, and a current patch including tests. I just ran out of time. There's quite a few issues still with patches to review. And I don't understand your last comment on this issue, Brett. Is that meant as a TODO for a Maven dev? Just an indication that there was an updated patch, as you said, so it was worth a look in the next release. I've every intention of continuing to work through the next release as soon as I have cycles again. Perhaps someone with more cycles will drop in and review / apply the patch to trunk sooner. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] Release Maven Release plugin version 2.1
Hi, We solved 17 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=12571 Staging repo: https://repository.apache.org/content/repositories/maven-002/ Source distribution: https://repository.apache.org/content/repositories/maven-002/org/apache/maven/release/maven-release/2.1/maven-release-2.1-source-release.zip SCM tag: http://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.1 Staging site: http://maven.apache.org/plugins/maven-release-plugin-2.1/ http://maven.apache.org/maven-release/staging/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Cheers, Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Release plugin version 2.1
+1 -- Pull me down under... On Tue, Oct 5, 2010 at 1:01 AM, Brett Porter br...@apache.org wrote: Hi, We solved 17 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=12571 Staging repo: https://repository.apache.org/content/repositories/maven-002/ Source distribution: https://repository.apache.org/content/repositories/maven-002/org/apache/maven/release/maven-release/2.1/maven-release-2.1-source-release.zip SCM tag: http://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.1 Staging site: http://maven.apache.org/plugins/maven-release-plugin-2.1/ http://maven.apache.org/maven-release/staging/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Cheers, Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Maven release plugin and GIT
Hello, I'm testing the maven release plugin (mvn -Darguments=-DskipTests org.apache.maven.plugins:maven-release-plugin:2.0:prepare) with a maven project and got this error: ... [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /root/git-repos4/project2 git add -- pom.xml moduleA/pom.xml moduleB/pom.xml [INFO] Working directory: /root/git-repos4/project2 [INFO] Executing: /bin/sh -c cd /root/git-repos4/project2 git status [INFO] Working directory: /root/git-repos4/project2 [INFO] Executing: /bin/sh -c cd /root/git-repos4/project2 git commit --verbose -F /tmp/maven-scm-845822206.commit pom.xml moduleA/pom.xml moduleB/pom.xml [INFO] Working directory: /root/git-repos4/project2 [INFO] Executing: /bin/sh -c cd /root/git-repos4/project2 git symbolic-ref HEAD [INFO] Working directory: /root/git-repos4/project2 [INFO] Executing: /bin/sh -c cd /root/git-repos4/project2 git push http://172.17.27.218/project2 master:master [INFO] Working directory: /root/git-repos4/project2 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to commit files Provider message: The git-push command failed. Command output: error: Cannot access URL http://172.17.27.218/project2/, return code 22 fatal: git-http-push failed But if i use the git command push i don't have any problems: ~/git-repos4/project2# git push origin master Fetching remote heads... refs/ refs/heads/ refs/tags/ updating 'refs/heads/master' from 44728f87a5a6f90a0c8e131ad7749811ac133681 to 8a451fc775478c144686744a0b4c0490be23b0b9 sending 6 objects done Updating remote server info To http://localhost/project2/ 44728f8..8a451fc master - master Could be an authentication problem? I tried as well the command with username and password (mvn -Darguments=-DskipTests -Dusername=admin -Dpassword=admin org.apache.maven.plugins:maven-release-plugin:2.0:prepare), but got the same error. I tried to change the scm connection in the POM file, but got the same error: scm connectionscm:git:http://admin:ad...@172.17.27.218/project2/connection /scm I have the file .netrc configured with host, username and password. Does Maven use this file? Any ideas? regards, Santos -- View this message in context: http://maven.40175.n5.nabble.com/Maven-release-plugin-and-GIT-tp3046833p3046833.html Sent from the Maven - SCM mailing list archive at Nabble.com.
Re: maven-release-plugin release?
Hi Brett, Brett Porter wrote: On 17/09/2010, at 2:23 AM, Jörg Schaible wrote: Hi Baptiste, Baptiste MATHUS wrote: Well, from my understanding, this is not a regression. What Paul says in the end http://jira.codehaus.org/browse/MNG-4687?focusedCommentId=235494page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment- tabpanel#action_235494is not a workaround, but the right way to go. It *is* a regression with the release plugin, if you cannot release with such a pom. See the first comment. If I understand correctly, it's more that the release plugin doesn't yet understand relativePath/releativePath, which is something new in Maven 3 to represent no relative path for the warning? Yep. That's what the reporter in the first comment said. - Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-release-plugin release?
I answered that since I opened the attached test project, and I didn't see any relativePath tag anywhere (though I might have missed it). Cheers 2010/9/17 Jörg Schaible joerg.schai...@gmx.de Hi Brett, Brett Porter wrote: On 17/09/2010, at 2:23 AM, Jörg Schaible wrote: Hi Baptiste, Baptiste MATHUS wrote: Well, from my understanding, this is not a regression. What Paul says in the end http://jira.codehaus.org/browse/MNG-4687?focusedCommentId=235494page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment- tabpanel#action_235494is not a workaround, but the right way to go. It *is* a regression with the release plugin, if you cannot release with such a pom. See the first comment. If I understand correctly, it's more that the release plugin doesn't yet understand relativePath/releativePath, which is something new in Maven 3 to represent no relative path for the warning? Yep. That's what the reporter in the first comment said. - Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: maven-release-plugin release?
Baptiste MATHUS wrote: I answered that since I opened the attached test project, and I didn't see any relativePath tag anywhere (though I might have missed it). The problem is that the author of comment #1 did not open a new issue for the release plugin but used instead this maven issue to report a problem with the proposed solution. However, if a new release of the release plugin is coming, it should work now flawlessly with M3 (resp. the documented migration solutions). - Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-release-plugin release?
So... does someone want to open it? :) On 17/09/2010, at 1:07 AM, Jörg Schaible wrote: Baptiste MATHUS wrote: I answered that since I opened the attached test project, and I didn't see any relativePath tag anywhere (though I might have missed it). The problem is that the author of comment #1 did not open a new issue for the release plugin but used instead this maven issue to report a problem with the proposed solution. However, if a new release of the release plugin is coming, it should work now flawlessly with M3 (resp. the documented migration solutions). - Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-release-plugin release?
On 17/09/2010, at 1:07 AM, Jörg Schaible wrote: Baptiste MATHUS wrote: I answered that since I opened the attached test project, and I didn't see any relativePath tag anywhere (though I might have missed it). The problem is that the author of comment #1 did not open a new issue for the release plugin but used instead this maven issue to report a problem with the proposed solution. However, if a new release of the release plugin is coming, it should work now flawlessly with M3 (resp. the documented migration solutions). Ok. Would someone familiar with the issue like to open it with the appropriate amount of detail? Thanks, Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-release-plugin release?
Brett Porter wrote: On 15/09/2010, at 2:26 PM, Mark Derricutt wrote: Hey guys, I was wondering what was happening with the new release of the maven-release-plugin? Things seemed to go quiet on that front this past week or so... I see that the SCM plugin got released tho, would be good to get the release plugin to come along for the ride as well... Yah, I lost the window of opportunity I had originally, and things have kept coming up since. I'm getting back to it now... there were nearly 30 issues with recent patches on them that I'd like to have a quick look at, then try for the release again. Beyond that, there's another 30 issues marked as having patches that are somewhat older that would be worth going through and a number of highly voted issues that seem fixable. Might be good for a follow up release. There's also a regression reported in: http://jira.codehaus.org/browse/MNG-4687 - Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-release-plugin release?
Well, from my understanding, this is not a regression. What Paul says in the end http://jira.codehaus.org/browse/MNG-4687?focusedCommentId=235494page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_235494is not a workaround, but the right way to go. See also https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes#Maven3.xCompatibilityNotes-ParentPOMResolutionor http://docs.codehaus.org/display/MAVENUSER/Iron+Fist+of+Maven+3.0+transition+pack Cheers. 2010/9/16 Jörg Schaible joerg.schai...@gmx.de Brett Porter wrote: On 15/09/2010, at 2:26 PM, Mark Derricutt wrote: Hey guys, I was wondering what was happening with the new release of the maven-release-plugin? Things seemed to go quiet on that front this past week or so... I see that the SCM plugin got released tho, would be good to get the release plugin to come along for the ride as well... Yah, I lost the window of opportunity I had originally, and things have kept coming up since. I'm getting back to it now... there were nearly 30 issues with recent patches on them that I'd like to have a quick look at, then try for the release again. Beyond that, there's another 30 issues marked as having patches that are somewhat older that would be worth going through and a number of highly voted issues that seem fixable. Might be good for a follow up release. There's also a regression reported in: http://jira.codehaus.org/browse/MNG-4687 - Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
