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

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

----- Original Message -----
> 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. 

I'm not doubting that, but its not the majority.
 
> 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.

Yes, but note how maven haven't done that nor have the eclipse platform - m2e 
would be hurting itself by doing this move.
 
> 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.

If you could say "hey - we are upgrading to require Java 7 because it will make m2e 5 times faster" or 
"now more projects can load and you can your work done with maven" then there would actually
be *value* in this move. But for now its just about a no doubt nice java syntax but
its not going to rock any users world in a good way - it will just make life harder for them.
  
> Java6, I believe, has hit EOL no?  It is no longer a supported product
> at Oracle.  

Not correct, they have extended the support.

> Companies that do not move have already decided that
> stability is a higher priority than features.

Just because you dont update Java VM does not mean you dont want or need new features of the things build on top.

Moving Java 7 is not going to provide any new features to m2e, right? so that is not really relevant here.

Just to put some context, when we had to migrate Hibernate from 1.4 to 1.5 of java - that was done piecemal
- only making the parts of Hibernate that needed i.e. annotations a separate codebase - once Java 5 was majority
*then* hibernate core could start using java 5 features.

Yes, we would love doing hibernate dev with Java 5 features but doing so would alienate tons of uses; thus it was not done.
But we could still innovate and provide new features...

/max 
> 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.
> _______________________________________________
> m2e-users mailing list
> m2e-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-users
> 

-- 
/max