Re: [m2e-dev] [m2e-users] moving m2e to java7 past kepler sr0

[Max Rydahl Andersen <max.andersen@xxxxxxxxxx>]

----- Original Message -----
> Just to confirm I understand you correctly. JBossTools will support
> java6 throughout 2014. If m2e 1.5 requires java7, JBossTools will have
> to stay on m2e 1.4. Do I get this right?

Eclipse itself will support Java6 throughout 2014 as far as I can see.

And yes, we wouldn't be able to pickup this new version of m2e before we 
see actual usage of Java 6 runtimes on developers desktop decline significantly.

If m2e was just an "addon" in the overall eclipse ecosystem I could see it be ok,
but with m2e be a fundemental part of the Eclipse IDE experience and that the feature
in Java 7 you want to use provides zero to little value to actual users I find
it very wrong for m2e to require Java 7 for execution before Eclipse EPP requires it
too.
  
/max
> 
> --
> Regards,
> Igor
> 
> On 2013-05-30 7:42 AM, Max Rydahl Andersen wrote:
> >
> >
> > ----- Original Message -----
> >> Hello, Max,
> >>
> >> This is most likely the default jvm users have on their classpath and
> >> does not tell if 1.6 is a hard requirement for these users or they can
> >> run m2e with java7 just as easily.
> >
> > Neither you nor I can prove that - but I can just say that Windows XP is
> > also
> > still more used than all Linux and OSX users combined.
> >
> > Corporate decisions/standards made them have to stay there - same applies
> > to Java versions.
> >
> > Many will be forced on Java 6 and lets say if they even were able to run
> > Java 7
> > then if m2e changes to force Java 7 eclipse will simply just silently not
> > load
> > m2e and *all* the plugins that depend on it.
> >
> > Imagine if maven core itself would require Java 7 - that would be seriously
> > bad for its
> > usage too.
> >
> >> Also keep in mind that this proposed change will happen in September at
> >> the earliest, but I am totally fine waiting until Luna as long as m2e
> >> master is on java7. Many users will have moved to java7 by then, and
> >> those who don't or can't, will probably stick with an older version of
> >> m2e anyways and won't be affected by the change.
> >
> > I was hoping we could continue using new versions of m2e in JBoss Tools -
> > if
> > this changes we and many others can't.
> >
> > That would be seriously bad IMO.
> >
> > /max
> >
> >>
> >> --
> >> Regards,
> >> Igor
> >>
> >> On 2013-05-30 4:55 AM, Max Rydahl Andersen wrote:
> >>> Hey Igor,
> >>>
> >>> I completely understand the reasoning for moving, but I hate to be the
> >>> one
> >>> break the news but users are not by far having adopting Java 7 as their
> >>> preferred
> >>> runtime.
> >>>
> >>> I've kept eye on this for the last ~2+ years via the JBoss Tools usage
> >>> collection and
> >>> even though Java 7 is definitely rising it is moving much slower than I
> >>> think most
> >>> developers think.
> >>>
> >>> The current stats from JBoss Tools last few days usage collection shows
> >>> the
> >>> following:
> >>>
> >>> 1.8.0	55	0.16%
> >>> #N/A	177	0.52%
> >>> 1.5.0	363	1.06%
> >>> 1.7.0	14116	41.08%
> >>> 1.6.0	19648	57.18%
> >>> Grand Total	34359
> >>>
> >>> Thus Java 6 is still the most dominant Java used to *run* eclipse with
> >>> (at
> >>> least in JBoss Tools land :)
> >>>
> >>> Note, a few months ago Java 7 was just a 20% so it is growing - but I
> >>> don't
> >>> expect Java 7 to be *really* dominant (>80% as Java 6 was for the last 2+
> >>> years) before next year.
> >>>
> >>> Thats the time where one could consider moving things like Eclipse IDE
> >>> and
> >>> m2e to start requiring Java 7 for core technologies like m2e.
> >>>
> >>> Take this is as a friendly data-backed Please Don't exclude 50% of our
> >>> users from being able to use Maven!
> >>>
> >>> /max
> >>>
> >>>
> >>> ----- 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-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
> 

-- 
/max