[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-dev] [m2e-users] moving m2e to java7 past kepler sr0
|
Hey!
Can we align this somehow with the release train and what the release
train defines as the supported platforms? I think this is Java6 + Java7
for Kepler (I guess for SR0-2). If Luna continues to support Java6 as a
runtime platform, I think it would be good if m2e would also continue to
run on Java6.
Just my 2 cents,
-Martin
On 30.05.13 13:44, Igor Fedorenko wrote:
I don't plan to downcompile m2e to java6 even if this is supported, I
plan to require java7 when running m2e.
--
Regards,
Igor
On 2013-05-30 7:37 AM, Max Rydahl Andersen wrote:
----- Original Message -----
I totally agree with the change to Java7. just because when using Java7
you can still produce binaries to the target system in Java6 (if were
required).
If the binaries can run on Java 6 then that is all fine - but I read the
request that Java 7 would be required to run.
People that don't want to change and use new features that only can be
provided by new Java version should stay with the old version. The same
will happen for teams that would like to use new Jetty 9 and its news
features.
Jetty 8 and 9 can coexist in eclipse - m2e old version and new cannot.
Very different things.
Most people that I know and use Mac is moving to Java7 due the security
issues reported with Java6. Btw, Mountain Lion didn't come with Java and
to install one you should use Java 7.
Most people I know are also on Java 7, but that is not the users that
there are the most of.
This is called observer bias and something to be vary aware of and why we
collect actual user data instead of looking at the people we actually
meet in our day to day
work which tend to be years ahead of the main user adoption.
/max
On 30/05/13 07:00, Martin Lippert wrote:
Hey!
Thanks, Max, for the heads-up here.
Yes, I can confirm very similar numbers from both the Spring Tool
Suite and the Groovy/Grails Tool Suite. We have about 55% running on
Java6. This number is even a bit higher on Mac (about 60%).
I also share the motivation for moving to Java7, but it would cut off
something between 50% and 60% of our users (roughly speaking). So
please don't exclude them from new m2e versions that soon...!!! :-)
Thanks!!!
-Martin
On 30.05.13 11:51, Max Rydahl Andersen wrote:
I've pinged Martin Lippert from STS who confirmed similar numbers but
he'll follow on this thread with the exact numbers.
----- Original Message -----
I'd like to propose moving m2e to require java7 execution environment
after Kepler SR0 is out. I am getting really addicted to
try-with-resources syntax [1], and with java6 past it's eol [2]
already,
I see little/no reasons to stick with this version any longer.
Does anyone have a good reasons to stay with java 6 past this coming
June? ("my IT department is too retarded to allow java7" is probably
not
a good reason).
[1]
http://docs.oracle.com/javase/tutorial/essential/exceptions/tryResourceClose.html
[2] http://www.oracle.com/technetwork/java/eol-135779.html
--
Regards,
Igor
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev
