For the record, maven2 does not have precise enough dependency resolution to handle the somewhat crazy hoops we jump through to test surefire with surefire itself. So although we're still 2.2.1 compatible, we've required 3.x to build for some time.
Kristian 2014-11-02 18:18 GMT+01:00 tibor17 <[email protected]>: > Karl, the README.txt will force the users to prepare for Maven 3. > IMHO the SUREFIRE 3.0 would completely switch to Maven 3. > Then we can use prerequisites with enforcer declaring the same min version > of Maven dist. > We will have chance to use Java Generics instead of using java.lang.Object > in public API, remove jdk-1.3 and 1.4 profiles, declare surefire|failsafe > property prefixes, use JDK 6 and Java 1.6 API, and break the backwards > compatibility. > > The Java 6 is not maintained by the Oracle. It would be nice to see the > Maven running on the top of Java 8 in the near future. I am not sure if we > would have any bigger benefits from JDK 7 except for NIO and GC > improvements. > > > > ----- > BR, tibor17 > -- > View this message in context: > http://maven.40175.n5.nabble.com/VOTE-Release-Maven-Surefire-Plugin-version-2-18-Take-2-tp5812277p5812412.html > Sent from the Maven Developers mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > 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]
