On 29/11/2012 10:17 AM, Markku Saarela wrote:
People is stuck for old Java versions due to the fact that for example
organizations are using IBM WebSphere and do not upgrade those
immediately when new version of WAS is released. WAS 6.1 which was
released in 2006 and just add support for JDK 1.5 not 1.6. It is WAS 7
which has JDK 6 support build in from beginning 2008. Just latest WAS
8.5 has possibility to use JDK 7.
Lot of organizations is still running with WAS 6 .
You are saying that for those organizations, Java 6 and 7 broke upward
compatibility?
We never had that problem but I guess IBM's coding was a bit too tied to
features that were deprecated and then removed in java 6 or 7.
What would it mean for them if Maven had a default of Java 7.
Could they not just change the Java setting to 1.4 or 1.3 and still run
Maven and compile their Websphere apps?
Is it not possible to run Maven in a JRE7 VM and compile code with a 1.3
compiler?
I think that we have done that in the past where our app was being built
using 1.5 but we had our Eclipse and Maven running in a 1.6VM.
Ron
Markku
On 11/29/2012 04:55 PM, Ron Wheeler wrote:
Java 7 has been out for almost a year and a half.
Java 6 was released in 2006
What keeps people on old versions for over 8 years(1.5)?
We have tried to keep up with the times and feel that we got a lot of
performance improvements over time without any pain as we changed
versions.
There does not seem to be any problem using Maven to compile Java
version 7. Java 7 certainly runs Maven just fine.
Are we not just talking about changing the default to 7 not forcing
everyone to use 7 or run their IDE on 7 or am I missing something?
They can still select the compiler that they want if they are not up
to date.
Ron
On 29/11/2012 9:19 AM, Stephen Connolly wrote:
That is a fair point. And I concur, that until core ups its minimum JRE
requirement, compiler shouldn't move past that...
Raises the question should core up to 1.6... I don't see a pressing
need
yet...
Lambdas are not until 1.8, and we don't do the crazy generics stuff
that,
for example, forced Jenkins to require 1.6 to build. So without a
pressing
need, I think core should stay on 1.5 for now
On 29 November 2012 10:39, Jochen Wiedmann
<jochen.wiedm...@gmail.com>wrote:
Leaving aside questions of compatibility, Java 7 as compiler
default would
be a poor choice. After all, that would require JRE 7 as a standard
for
running Maven, or using one of the Eclipse compilers. Otherwise,
that would
be unsupported by the compiler.
On Wed, Nov 28, 2012 at 8:43 PM, Ron Wheeler <
rwhee...@artifact-software.com
wrote:
+1
On 28/11/2012 1:36 PM, Mark Derricutt wrote:
Now that Oracle are controlling Java on OSX we can no longer "blame
Apple" - I'd love to see the default become Java 7 now.
And if one needs to lock down to the older versions, lock them down.
On 29/11/2012, at 7:07 AM, Curtis Rueden <ctrue...@wisc.edu> wrote:
Good to know that Maven is now only 8 years behind.
I blame Apple.
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
------------------------------**------------------------------**---------
To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org<
users-unsubscr...@maven.apache.org>
For additional commands, e-mail: users-h...@maven.apache.org
--
The best argument for celibacy is that the clergy will sooner or later
become extinct.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
