Well, as long as plugins declare support for Maven [2.0,2.2) strictly
speaking we should be building those on Java 1.4
If the plugin declares support for Maven [2.2,3.2) then we need to ensure
Java 1.5 support.
If a plugin declares that it requires Maven 3.2 then we are only needing to
ensure
Um, yes, me! :-)
Seriously we are still stuck on Java 1.5/WAS 6.1/COBOL for at least another
year. Until we move to java 6 (or 7) depending on what oracle will support.
-Chris, representing 0.0001% :-)
Sent from my iPhone
On 12/11/2013, at 4:41 PM, Romain Manni-Bucau rmannibu...@gmail.com
Well it's not like Maven [,3.2) is critically broken... so you'll just have
to live with that toolchain... anyways, toolchains support should resolve
issues down to 1.5 at least (or older if you can live with older versions
of surefire plugin)
On 12 November 2013 11:02, Chris Graham
Hm..
While WAS 6.1 is still certainly still an IBM-supported version, I can
certainly feel your JDK version pain there, Chris.
Just out of curiosity - would you claim that the motives for staying on
such an old application server version would be motivated more by economy
than technology? Or are
The client in question is using Oracle's CCB (Customer Care and Billing)
their package for power companies.
So moving is not a trivial decision, as Oracle have to say if they are
prepared to support the specific combination we have. AIX level, WAS
version, JDK version etc. The joys of commercial
http://maven.apache.org/developers/release/maven-project-release-procedure.html
says so. I don't know where I'm going to get that environment.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands,
i guess it's the only way to definitely ensure backwards compatibility
open potential solution would be to use vagrant, I use it to ensure
developers as using the same base build setup and the files can be source
controlled
On 11 November 2013 22:39, Benson Margulies bimargul...@gmail.com
Isnt the question: is there still someone needing j5? Almost all apache
projects and others moved to j6 at least
Le 11 nov. 2013 23:53, John Patrick nhoj.patr...@gmail.com a écrit :
i guess it's the only way to definitely ensure backwards compatibility
open potential solution would be to use
I don't know where I'm going to get that environment.
Everything is still accessible in Oracle Java Archive:
http://www.oracle.com/technetwork/java/archive-139210.html
Dawid
-
To unsubscribe, e-mail:
