The other side would say we are enabling crap code on unsupported,
unprotected jvms. New Java 6 development will die (more quickly) when
big libraries like commons-io stop supporting it. As it is, we are the
Java 6 drug dealers.
On 04/26/2016 09:28 AM, Emmanuel Bourg wrote:
Le 26/04/2016 14:57, Dave Brosius a écrit :
The extra management that's required is not worth the
2 people who want a new version of commons-io for java 6. We are talking
about an end of life date coming up on 4 years.
There is no extra management besides configuring the Maven compiler
plugin to generate Java 6 bytecode and refraining from using Java 7 APIs
unless absolutely required (and preferably in dedicated classes).
commons-io is our most used component, we have to be conservative as it
impacts many projects.
Emmanuel Bourg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
