Skip to main content
[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
To  be sure to understand, Igor when you say "user" you mean "developers"  !

In our project, the build target is still 1.6 but the build environnement is 1.7 (to use NIO2 in my case in mojo). 

IMHO, the question is "is there any issue with third party plugins/mojo with java 1.7?". 

+1 on life easier with TWR && NIO2.


On Thu, May 30, 2013 at 10:16 PM, Igor Fedorenko <igor@xxxxxxxxxxxxxx> wrote:
We obviously want to avoid "alienating significant part of m2e users",
and this is exactly why I asked the question instead of just making the
change.

I fully realize some users will not be able to upgrade their java
version and will have to stay on an older version of m2e. Problem is, we
don't have any data to judge what proportion of users will and will not
be able to upgrade because of java version.

Also, I honestly believe that my productivity and productivity of other
m2e developers and contributors is more important for m2e project than
costs savings "IT department of a large bank" might get by sticking to
an old java version.

--
Regards,
Igor

On 2013-05-30 2:59 PM, Tonny Madsen wrote:
Igor,

You write: "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)."

I don't know if you ever worked in the IT department of a large bank,
offshore consultancy company or a similar institution, but... these
organizations want to control the amount of support and maintenance by
locking down the used platforms. "Retarded"??? I'm pretty sure most IT
people would make the same choices given the available resources in the
IT departments!

Java 7 might make your life easier, but is that really reason enough to
alienate an insignificant part of your users?

/Tonny

--
Tonny Madsen
My profiles: LinkedIn <http://www.linkedin.com/in/tonnymadsen> Twitter
<http://twitter.com/tonnymadsen> Blogger
<http://tonnymadsen.blogspot.dk/> SlideShare
<http://www.slideshare.net/nonty>


On Thu, May 30, 2013 at 4:10 AM, Igor Fedorenko <igor@xxxxxxxxxxxxxx
<mailto:igor@xxxxxxxxxxxxxx>> wrote:

    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>
    https://dev.eclipse.org/__mailman/listinfo/m2e-users
    <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



--
"Computers are useless. They can only give you answers."
- Pablo Picasso -

Back to the top