Am 07/24/13 04:00, schrieb jieryn:
> 
> Move forward or die. If you are stuck on 1.5, you can continue to use
> a full stack that is already supported. I am so sick of hearing people
> complain that they will be broken if a JDK migration to a newer
> version is undertaken. No, you are not broken, you simply can not
> upgrade. There is a huge difference between being broken and not
> having an upgrade path.

Upgrade to Java 7 because you make use of the new APIs Java 7 introduces
or stay with Java 5. Java 6 does not introduce anything interesting to
Maven core. Java 7 does.

> This form of anti-migration argument has less value than a "without
> any requirement" argument for not migrating.

I do not argue against migrating. I do argue against migrating without
any reason.

Since this is a vote thread:

+1000 (non-binding) as long as someone explains why there is any need to
change '-target 1.5' to '-target 1.6'. Seriously. I don't get it. You
are really just changing the class file version and nothing else without
any reason. I would like to know the reasioning. Nothing more.

-- 
Christan


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to