issues for 3.2.6 have already been pushed forward to 3.3.0 *before* the
Java7 decision. And that's fine by me.
As Dennis already suggested: after 3.3.0 push JDK requirement to 1.7 and
call this Maven 3.4.0
A JDK requirement has too much impact for a 3.3.1, but IMHO it's not worth
a 4.0.0
Also see previous releases when we moved forward to Java5 (M2.2) and Java6
(M3.2)
Op Sun, 08 Mar 2015 21:33:38 +0100 schreef Tibor Digana
<tibordig...@apache.org>:
@Robert
source=target=1.7 after M3.3.0? You mean 3.3.1?
A bit strange to make it in an incremental version since a user would not
imaging a fix version to break the system requirements in his CI
regarding
JDK installation.
Currently the release notes for 3.2.6 is empty.
So if there's really nothing to fix in 3.2.6, I would suggest to jump to
3.3.0 with JDK 7.
http://jira.codehaus.org/browse/MNG/fixforversion/20821
--
View this message in context:
http://maven.40175.n5.nabble.com/move-maven-core-to-java-7-tp5827988p5828522.html
Sent from the Maven Developers mailing list archive at Nabble.com.
---------------------------------------------------------------------
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
