[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-users] moving m2e to java7 past kepler sr0
|
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.
I'm not saying it would be sufficient. Some orgs would choose to stay
behind. It is not reasonable to make product decisions on a tool
primarily on the basis of self-imposed platform limitations in stubborn
customer sites.
Java6, I believe, has hit EOL no? It is no longer a supported product
at Oracle. Companies that do not move have already decided that
stability is a higher priority than features.
c.
On 30 May 2013, at 4:42, Max Rydahl Andersen wrote:
Imagine if maven core itself would require Java 7 - that would be
seriously bad for its
usage too.
