I'll write this up in the site docs, but for now I'll explain here:
There are a couple of reasons for moving 2.1 => 2.2 directly. First,
we've moved to a requirement on JDK 1.5. While we had decided to do this
for 2.1.0, we never enforced it or changed the Maven binaries
themselves. To keep from surprising users of 2.1.0 with an abrupt JDK
upgrade requirement in 2.1.1, we're just moving to 2.2.0.
The other reasons a probably a little more, well, gray. First, we've
removed support for version-expression resolution in the POM on
install/deploy. You can see MNG-4223 for more discussion on this and a
link to a more in-depth exploration of the issue. Also, we've introduced
some new default execution IDs for configuring goals that are bound to
the lifecycle via package mappings, and for goals executed directly from
the command line. These new executionIds represent some new assumptions
made by Maven, and conceivably could produce collisions with existing
executionIds for users. You can see MNG-3401 and MNG-3203 for more
discussion and links to documentation that will eventually land on the
Maven website.
While I understand your hesitation to move to a 2.2.0-type release, this
isn't exactly the same as a 2.0 release. Sure, there are major changes
here, but the fact is 2.1.0 was our most tested, scrutinized release to
date, and 2.2.0 builds on the two or three problems that appeared in
that release. Obviously it's up to you, but I'd highly recommend using
2.2.0.
-john
Paul Benedict wrote:
Personally, I will not be upgrading to Maven 2.2 until the next patch
release. I am skipping 2.1 because there is no 2.1.1. Being
conservative in my approach, I find it just too risky inside an
organization to bring in upgrades without at least one patch release.
Will anyone yet document justification for upgrading to 2.2/2.1 from
2.0? JIRA notes are for the "geeks" but a general summary would be
worthwhile.
I disagree with deleting branches. I think that's extreme.
Paul
On Tue, Jun 30, 2009 at 8:05 AM, Jason van Zyl<[email protected]> wrote:
On 29-Jun-09, at 7:54 PM, Brian Fox wrote:
Yeah get rid of it. Is there really demand for the fixed in 2.0.11? I
feel like it's EOL now.
I would guess the vast majority of users are still using the 2.0.x line
because the 2.1.x and 2.2.x lines have come out very quickly and users will
probably let those bake awhile. I think there are still too many
inconsistencies between the lines and change between minor versions happened
a little too quickly for people to absorb. I think the 2.0.x line will still
be in widespread use for the next year.
On Mon, Jun 29, 2009 at 7:33 PM, Brett Porter<[email protected]> wrote:
Just a matter of clarity. If its not there, there will be no question
about
whether to merge to it or not.
- Brett
On 30/06/2009, at 4:12 AM, Paul Benedict wrote:
Hmm...
- declare 2.0.x EOL after that release and delete the branch
What harm is there in keeping it around? Even if you never return to
it, it doesn't cost you anything to keep it.
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/SonatypeNexus
http://twitter.com/SonatypeM2E
----------------------------------------------------------
Three may keep a secret if two of them are dead.
-- Benjamin Franklin
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
