This is chicken-and-egg situation. We won't use java 7 features unless
the code targets java 7.
Try-with-resources and multi-exception catch are the too features I'd
like to start using throughout the code. Although not "critical" per se,
I think they make writing correct maintainable code noticeably easier.
Improvements to standard library, nio in particular, is another big
reason for me. For example, Files#walkFileTree is significantly faster
than comparable File-based implementation on large source trees. Knowing
the core is on java 7 will allow us use that in plexus-utils for example.
Besides, java 7 is EOL'ed by Oracle next month. Yes, many organizations
still use java 6 (and java 5), but the same organizations are not likely
to move to use latest maven features any time soon either.
--
Regards,
Igor
On 2015-03-05 7:59, Robert Scholte wrote:
I don't know the numbers, but I think JDK6 is still used a lot by the
community.
Current code builds fine with JDK6.
Which JDK7 specific features do you want to use, which are not possible
with the current codebase?
Without any critical codechanges I'd go for -1.
Robert
Op Thu, 05 Mar 2015 13:19:11 +0100 schreef Igor Fedorenko
<[email protected]>:
With maven core version change to 3.3.0 on master, any objections I
change compile source/target to java 7?
--
Regards,
Igor
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
