On 2013-05-31 08:34, Tonny Madsen wrote:
> It's just a statement that new stuff will require other new stuff.

For me the operational word is "require" :-)

And slightly easier development is *not* a hard requirement in my book. Most of the problems the new resource construct can avoid can also be avoided using findbug, checkstyle, etc...

Yes, of course. But you can't deny that the new constructs will increase code quality nevertheless. Not everyone is using (or even would like to use) those tools. And then there's all new functionality. Support for symlinks to name one. Far better integration with dynamic languages is another.

At the end, the question is, who is paying? Do we reward the companies that allow their software developers to only upgrade parts of their development environment at the expense of everyone else? Or do we simply state that if you want to be on the "using the latest and greatest" train, then that will require you to use a more recent JVM then the one who has already reached its EOL! To me, that choice is simple. If there's a problem with "installing", simply do as Renat suggests. Problem solved.

- thomas


/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 Fri, May 31, 2013 at 7:45 AM, Thomas Hallgren <tho...@tada.se <mailto:tho...@tada.se>> wrote:

    On 2013-05-30 22:19, Tonny Madsen wrote:

        No so... Remember that Eclipse can be installed everywhere -
        Java cannot.


    That is a good point. However, I've never been able to understand
    why inertia in some organizations product department should be
    allowed to hold back technology progress for the developers. If an
    organization does allow upgrades of Eclipse (and hence upgrades of
    their development environments), then I find it very likely that
    they will allow the developers to use Java 7 as well. The fact
    that the developed product then runs on a Java 6 JVM is not
    relevant. m2e is all about development. The resulting artifact may
    well run on much older platforms.

    So, It's not like anything is taken away. It's just a statement
    that new stuff will require other new stuff. If you don't like new
    stuff, then just stay with the old! But don't expect all others to
    do so just because.

    - thomas


    _______________________________________________
    m2e-users mailing list
    m2e-users@eclipse.org <mailto:m2e-users@eclipse.org>
    https://dev.eclipse.org/mailman/listinfo/m2e-users




_______________________________________________
m2e-users mailing list
m2e-users@eclipse.org
https://dev.eclipse.org/mailman/listinfo/m2e-users

_______________________________________________
m2e-users mailing list
m2e-users@eclipse.org
https://dev.eclipse.org/mailman/listinfo/m2e-users

Reply via email to