[
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
|
If you have specific proposals how to make m2e easier to understand and
debug, provide submit your patches to m2e bugzilla and I'll be happy to
review them and provide feedback.
--
Regards,
Igor
On 2013-06-18 1:23 PM, Aliaksei Lahachou wrote:
Hello everyone,
I believe that m2e developers will benefit more by using clean code or
similar concept, than by adding some minor syntactic sugar of Java 7. I
had to debug through m2e when I created some complex connectors, and
this task is not for faint-hearted. I don't believe that Java 7 will
improve the situation a bit.
Regards,
htfv (Aliaksei Lahachou)
On Tue, Jun 18, 2013 at 10:17 AM, Igor Fedorenko <igor@xxxxxxxxxxxxxx
<mailto:igor@xxxxxxxxxxxxxx>> wrote:
This discussion is about version of java required to run m2e and has
nothing to do with the version of java used by the projects developed
using m2e. You can continue to compile for and run with any version of
java supported by JDT, which I believe is still something as old as 1.0.
--
Regards,
Igor
On 2013-06-18 11:24 AM, Maxime HAMM wrote:
Hi
As someone wrote few weeks ago, in big companies moving from
java 5 or 6
to 7 s a big deal and a mid-term project.
I'm responsible of software developments in such company…
developers are
working on about 30 java products. Using most of time java 6 and
java 7
for recent projects.
For oldest one I do not want to invest on upgrading them… also I
do not
want developers to maintain two development environments in
parallel…
That's not fun, but that is an economic and industrial reality !
If you decide not to support java 6 anymore, I will have to
decide *not*
to move to Kepler… if I will not be able to do it next year I
will be in
trouble regarding the use of eclipse…
Maxime
Envoyé de mon iPhone
Le 17 juin 2013 à 19:46, Igor Fedorenko <igor@xxxxxxxxxxxxxx
<mailto:igor@xxxxxxxxxxxxxx>
<mailto:igor@xxxxxxxxxxxxxx <mailto:igor@xxxxxxxxxxxxxx>>> a écrit :
I do not think waiting for entire release train to move to
java7 is
reasonable. Different release train participants have
different target
audience, and I don't see why m2e has to be limited by one
of 100+ other
projects that absolutely has to run on java 5 (or java 6).
--
Regards,
Igor
On 2013-06-17 9:08 PM, Martin Lippert wrote:
Hey!
No thoughts about my suggestion from some time ago?
Cheers,
-Martin
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
<http://docs.oracle.com/javase/tutorial/essential/exceptions/tryResourceClose.html>
[2]
http://www.oracle.com/__technetwork/java/eol-135779.__html
<http://www.oracle.com/technetwork/java/eol-135779.html>
--
Regards,
Igor
_________________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
<mailto:m2e-users@xxxxxxxxxxx>
<mailto:m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>>
https://dev.eclipse.org/__mailman/listinfo/m2e-users
<https://dev.eclipse.org/mailman/listinfo/m2e-users>
_________________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
<mailto:m2e-dev@xxxxxxxxxxx>
<mailto:m2e-dev@xxxxxxxxxxx
<mailto:m2e-dev@xxxxxxxxxxx>>
https://dev.eclipse.org/__mailman/listinfo/m2e-dev
<https://dev.eclipse.org/mailman/listinfo/m2e-dev>
_________________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
<mailto:m2e-dev@xxxxxxxxxxx>
<mailto:m2e-dev@xxxxxxxxxxx
<mailto:m2e-dev@xxxxxxxxxxx>>
https://dev.eclipse.org/__mailman/listinfo/m2e-dev
<https://dev.eclipse.org/mailman/listinfo/m2e-dev>
_________________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx <mailto:m2e-dev@xxxxxxxxxxx>
<mailto:m2e-dev@xxxxxxxxxxx
<mailto:m2e-dev@xxxxxxxxxxx>>
https://dev.eclipse.org/__mailman/listinfo/m2e-dev
<https://dev.eclipse.org/mailman/listinfo/m2e-dev>
_________________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx <mailto:m2e-dev@xxxxxxxxxxx>
<mailto:m2e-dev@xxxxxxxxxxx <mailto:m2e-dev@xxxxxxxxxxx>>
https://dev.eclipse.org/__mailman/listinfo/m2e-dev
<https://dev.eclipse.org/mailman/listinfo/m2e-dev>
_________________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx <mailto:m2e-dev@xxxxxxxxxxx>
<mailto:m2e-dev@xxxxxxxxxxx <mailto:m2e-dev@xxxxxxxxxxx>>
https://dev.eclipse.org/__mailman/listinfo/m2e-dev
<https://dev.eclipse.org/mailman/listinfo/m2e-dev>
_________________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx <mailto:m2e-dev@xxxxxxxxxxx>
https://dev.eclipse.org/__mailman/listinfo/m2e-dev
<https://dev.eclipse.org/mailman/listinfo/m2e-dev>
_________________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx <mailto:m2e-dev@xxxxxxxxxxx>
https://dev.eclipse.org/__mailman/listinfo/m2e-dev
<https://dev.eclipse.org/mailman/listinfo/m2e-dev>
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev
