On 2013-05-30 17:29, Christian Gruber wrote:
Or, if maven (or its oem portions) were heavily used in an
organization and it depended on Java7, many organizations, even large
ones, would bump the version. Corporate inertia keeps people back,
but platform version churn is largely driven by the need to run the
tools a business needs to run. If Maven is strategic to that, it
provides pressure to upgrade.
Hear, hear.
Another argument is that if there's a need to stay on old software (Java
1.6 is old), then by all means, stay with old software. There's no
requirement to upgrade. But of course, that also means, stay with old
versions of m2e. So what's the real problem?
- thomas
_______________________________________________
m2e-users mailing list
m2e-users@eclipse.org
https://dev.eclipse.org/mailman/listinfo/m2e-users
