You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Stephen Connolly <st...@gmail.com> on 2012/01/03 16:18:06 UTC
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Posted by Kalle Korhonen <ka...@gmail.com>.
Gaah! I just managed to waste an hour hunting down an issue with a
suddenly failing release after a parent of a parent was changed to use
version 2.2.2 of the release plugin. The worst is that I now recall I
saw this thread a week ago.
Kalle
On Tue, Jan 3, 2012 at 1:20 PM, Stephen Connolly
<st...@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
>
> - 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" <ji...@gmail.com> wrote:
>
>> Greetings,
>>
>> On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt <ma...@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.
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Posted by Arnaud Héritier <ah...@gmail.com>.
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 <ji...@gmail.com> wrote:
> Greetings,
>
> On Tue, Jan 3, 2012 at 4:20 PM, Stephen Connolly <
> stephen.alan.connolly@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)
Posted by Jesse Farinacci <ji...@gmail.com>.
Greetings,
On Tue, Jan 3, 2012 at 4:20 PM, Stephen Connolly <
stephen.alan.connolly@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)
Posted by Stephen Connolly <st...@gmail.com>.
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" <ji...@gmail.com> wrote:
> Greetings,
>
> On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt <ma...@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)
Posted by Brett Porter <br...@apache.org>.
On 04/01/2012, at 7:58 AM, Jesse Farinacci wrote:
> Greetings,
>
> On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt <ma...@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
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
http://twitter.com/brettporter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Posted by Stephen Connolly <st...@gmail.com>.
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" <ji...@gmail.com> wrote:
> Greetings,
>
> On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt <ma...@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)
Posted by Stephen Connolly <st...@gmail.com>.
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 <ji...@gmail.com>:
> > Greetings,
> >
> > On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt <ma...@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-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Posted by Olivier Lamy <ol...@apache.org>.
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 <ji...@gmail.com>:
> Greetings,
>
> On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt <ma...@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-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Posted by Jesse Farinacci <ji...@gmail.com>.
Greetings,
On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt <ma...@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)
Posted by Stephen Connolly <st...@gmail.com>.
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 <ma...@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.connolly@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 <ma...@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.connolly@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-unsubscribe@maven.apache.org
>> >> For additional commands, e-mail: users-help@maven.apache.org
>> >>
>> >>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Posted by Stephen Connolly <st...@gmail.com>.
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 <ma...@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.connolly@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 <ma...@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.connolly@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-unsubscribe@maven.apache.org
>> >> For additional commands, e-mail: users-help@maven.apache.org
>> >>
>> >>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Posted by Olivier Lamy <ol...@apache.org>.
Hello,
I will stage an other RC today evening time (fr tz)
2012/1/4 Stephen Connolly <st...@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 <st...@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 <bi...@gmail.com>:
>> >> > On Tue, Jan 3, 2012 at 6:12 PM, Stephen Connolly
>> >> > <st...@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 <ma...@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
>> >> >>> brett@apache.org
>> >> >>> http://brettporter.wordpress.com/
>> >> >>> http://au.linkedin.com/in/brettporter
>> >> >>> http://twitter.com/brettporter
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>>
>> ---------------------------------------------------------------------
>> >> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> >> >>> For additional commands, e-mail: dev-help@maven.apache.org
>> >> >>>
>> >> >>>
>> >> >
>> >> > ---------------------------------------------------------------------
>> >> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> >> > For additional commands, e-mail: dev-help@maven.apache.org
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Olivier Lamy
>> >> Talend: http://coders.talend.com
>> >> http://twitter.com/olamy | http://linkedin.com/in/olamy
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> >> For additional commands, e-mail: dev-help@maven.apache.org
>> >>
>> >>
>>
>>
>>
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Posted by Stephen Connolly <st...@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 <st...@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 <bi...@gmail.com>:
> >> > On Tue, Jan 3, 2012 at 6:12 PM, Stephen Connolly
> >> > <st...@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 <ma...@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
> >> >>> brett@apache.org
> >> >>> http://brettporter.wordpress.com/
> >> >>> http://au.linkedin.com/in/brettporter
> >> >>> http://twitter.com/brettporter
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> ---------------------------------------------------------------------
> >> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> >>> For additional commands, e-mail: dev-help@maven.apache.org
> >> >>>
> >> >>>
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> > For additional commands, e-mail: dev-help@maven.apache.org
> >> >
> >>
> >>
> >>
> >> --
> >> Olivier Lamy
> >> Talend: http://coders.talend.com
> >> http://twitter.com/olamy | http://linkedin.com/in/olamy
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >>
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Posted by Olivier Lamy <ol...@apache.org>.
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 <st...@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 <bi...@gmail.com>:
>> > On Tue, Jan 3, 2012 at 6:12 PM, Stephen Connolly
>> > <st...@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 <ma...@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
>> >>> brett@apache.org
>> >>> http://brettporter.wordpress.com/
>> >>> http://au.linkedin.com/in/brettporter
>> >>> http://twitter.com/brettporter
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> >>> For additional commands, e-mail: dev-help@maven.apache.org
>> >>>
>> >>>
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> > For additional commands, e-mail: dev-help@maven.apache.org
>> >
>>
>>
>>
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Posted by Stephen Connolly <st...@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 <bi...@gmail.com>:
> > On Tue, Jan 3, 2012 at 6:12 PM, Stephen Connolly
> > <st...@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 <ma...@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
> >>> brett@apache.org
> >>> http://brettporter.wordpress.com/
> >>> http://au.linkedin.com/in/brettporter
> >>> http://twitter.com/brettporter
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>
> >>>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Posted by Olivier Lamy <ol...@apache.org>.
2012/1/4 Benson Margulies <bi...@gmail.com>:
> On Tue, Jan 3, 2012 at 6:12 PM, Stephen Connolly
> <st...@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 <ma...@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
>>> brett@apache.org
>>> http://brettporter.wordpress.com/
>>> http://au.linkedin.com/in/brettporter
>>> http://twitter.com/brettporter
>>>
>>>
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Posted by Benson Margulies <bi...@gmail.com>.
On Tue, Jan 3, 2012 at 6:12 PM, Stephen Connolly
<st...@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 <ma...@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
>> brett@apache.org
>> http://brettporter.wordpress.com/
>> http://au.linkedin.com/in/brettporter
>> http://twitter.com/brettporter
>>
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Posted by Stephen Connolly <st...@gmail.com>.
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 <ma...@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
> brett@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
> http://twitter.com/brettporter
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Posted by Brett Porter <br...@apache.org>.
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 <ma...@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
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
http://twitter.com/brettporter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2
(MNG-5224)
Posted by Ansgar Konermann <an...@googlemail.com>.
Am 03.01.2012 22:12, schrieb Benson Margulies:
> On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt <ma...@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-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Posted by Benson Margulies <bi...@gmail.com>.
On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt <ma...@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.connolly@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 <ma...@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.connolly@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-unsubscribe@maven.apache.org
>> >> For additional commands, e-mail: users-help@maven.apache.org
>> >>
>> >>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Posted by Jesse Farinacci <ji...@gmail.com>.
Greetings,
On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt <ma...@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)
Posted by Mark Derricutt <ma...@talios.com>.
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.connolly@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 <ma...@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.connolly@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-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Posted by Mark Derricutt <ma...@talios.com>.
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.connolly@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 <ma...@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.connolly@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-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Posted by Stephen Connolly <st...@gmail.com>.
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 <ma...@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.connolly@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-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Posted by Stephen Connolly <st...@gmail.com>.
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 <ma...@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.connolly@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-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Posted by Mark Derricutt <ma...@talios.com>.
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.connolly@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-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Posted by Mark Derricutt <ma...@talios.com>.
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.connolly@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-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Posted by Arnaud Héritier <ah...@gmail.com>.
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.connolly@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-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Posted by Arnaud Héritier <ah...@gmail.com>.
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.connolly@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-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>