I added that today, after Benjamin mentioned it.
Arnaud HERITIER wrote:
http://jira.codehaus.org/browse/MNG-4143Actually it's scheduled for 2.1.1
Arnaud
On Thu, Apr 23, 2009 at 10:49 PM, Dennis Lundberg <[email protected]>wrote:
Benjamin Bentmann wrote:
John Casey wrote:
Since we've already decided that 2.1.0 would be moving to Java 1.5 I
can't see the use in hanging onto the 1.4 requirement
Let me clarify that I'm fine with moving to Java 1.5 (hurray). My
concern was that this change is made between 2.1.0 and 2.1.1, i.e. it's
merely the version label that concerns me.
From a user's perspective, updating a tool to a new point release should
impose no suprises or migration work. But if someone developed a Maven
plugin and updated its dependencies from maven-project:2.1.0 to
maven-project:2.1.1 and thereby indirectly increased the JRE requirement
of this project, he might be suprised. If someone built a project
targetting Java 1.4 and has simply configured his JAVA_HOME to point at
JDK 1.4 (to catch accidental usage of new API), he will need to
configure the bootstrap class path or the toolchains to reach the same
effect when migrating from Maven 2.1.0 to 2.1.1.
IMHO, it doesn't matter what we previously planned for 2.1 regarding the
Java requirement. Reality is that the released Maven 2.1.0 requires only
Java 1.4 and it feels odd to me to have any point release of 2.1.x to
have higher requirements than the start of this development line.
In a related context, MNG-1948 looks like a new feature with significant
code changes, so I again wonder whether 2.1.1 is the proper bucket for
this instead of 2.2...
Enough philosophy from me, the last thing I suggest is that we at least
create a JIRA ticket for the Java version bump which shows up in the
release notes for users to easily notice.
Very well put Benjamin.
I have no objection to move to 1.5, but we can't do it for a point release.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Dennis Lundberg
---------------------------------------------------------------------
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]
