Re: Java 6 support

s and fixes that would be generally useful to a wide community. As part of a possible 4.0 release, we should review the deprecated code to try and prune as much as possible. -- View this message in context: http://apache-poi.1045710.n5. nabble.com/Java-6-support-tp5721373p5728121.html Sent from

Re: Java 6 support

> Andi just tried to use more generics in some places and this showed a > problem either in Java 9 or Java 6 and thus he reverted this change again. AFAIK this also happened when I've refactored the SL Common interfaces, but I've forgotten about it :S This is a bug in Java 6 ... there are a few

Re: Java 6 support

gt; > -- > View this message in context: http://apache-poi.1045710.n5. > nabble.com/Java-6-support-tp5721373p5728121.html > Sent from the POI - Dev mailing list archive at Nabble.com. > > - > To unsubscribe, e

Re: Java 6 support

and backport security fixes and fixes that would be generally useful to a wide community. As part of a possible 4.0 release, we should review the deprecated code to try and prune as much as possible. -- View this message in context: http://apache-poi.1045710.n5.nabble.com/Java-6-support

Re: Java 6 support

Then let's kick XMLBeans to POI 5.0 and drop Java 6 ASAP if it's preventing Java 9 support. Java 9 is just around the corner (July 27). We should aim to support Java 9 the day it's released so we're not a reason for other software projects to delay Java 9 adoption. Have we addressed the open

Re: Java 6 support

+1 for switching now or after POI 3.17 ... if we will do a 3.17 final soonish. I'm actually bringing this up, as I was facing again problems with generics bugs in Java 6 and independently had a devops discussion with fluxo yesterday, questioning me/us why we are still on Java 6 level. > If

Re: Java 6 support

Kotlin and other languages managed to > compile to Java 6 bytecode... > https://stackoverflow.com/questions/22610400/a-program- > made-with-java-8-can-be-run-on-java-7 > > On Jul 9, 2017 15:48, "Javen O'Neal" <one...@apache.org> wrote: > > +1 > > I'm in

Re: Java 6 support

ot; <one...@apache.org> wrote: +1 I'm in favor of dropping Java 6 support. If users still need to run new versions of POI on old JVMs, they should be able to cross-compile, though it may require some extra tools on their end to modify the bytecode to be compatible with and old JVM. If we can

Re: Java 6 support

out intermediate code, and somehow Kotlin and other languages managed to compile to Java 6 bytecode... https://stackoverflow.com/questions/22610400/a-program-made-with-java-8-can-be-run-on-java-7 On Jul 9, 2017 15:48, "Javen O'Neal" <one...@apache.org> wrote: +1 I'm in favor of drop

Re: Java 6 support

+1 I'm in favor of dropping Java 6 support. If users still need to run new versions of POI on old JVMs, they should be able to cross-compile, though it may require some extra tools on their end to modify the bytecode to be compatible with and old JVM. If we can figure out a way to maintain

Re: Java 6 support

It has been a while that we've discussed this topic ... or at least I couldn't find another more recent/decent thread ... [1] How about switching to Java 7 now? If we'd do, will we change to version 4 then? Andi [1] http://apache-poi.1045710.n5.nabble.com/Java-6-support-td5721373.html

Java 6 support

Oracle released Java 6 in 2006, ended support for Java 6 in 2013 and released Java 7 in 2011 and ended support in 2015. Java 8 was released in 2014. There are a few language features introduced in Java 7 that would be nice to use in POI. This would mean asking everyone to move off of Java 6, but

Re: Java 6 support

Hi, I think we should switch to Java 7 post-3.14, I don't think any of those things will reduce code size a lot, but most of these are quite useful as soon as you get used to them. Dominik. On Wed, Dec 23, 2015 at 10:52 AM, Javen O'Neal wrote: > Oracle released Java 6 in

Re: Java 6 support

I still use Java 6 with POI in production, and I would suggest that if you bump up the required java level and start using the new language features, then only do so when you bump the major version of POI. To me, bumping the required java is too big of a change for just a point release of

Re: Java 6 support

On Wed, 23 Dec 2015, Javen O'Neal wrote: Oracle released Java 6 in 2006, ended support for Java 6 in 2013 and released Java 7 in 2011 and ended support in 2015. Java 8 was released in 2014. Many of our users work for big conservative organisations, who'd much rather throw money at a vendor

Re: Java 6 support

According to [1], we ended support for JDK 1.5 in POI 3.11-beta 1. We added commons-logging, commons-codec, and log4j in that version, so maybe those libraries required Java 6+. None of our current dependencies require Java 7 yet. > I'm ambivalent on this issue, as see our web sphere environment

RE: Java 6 support

Hi, > I think we should switch to Java 7 post-3.14, I don't think any of those > things will reduce code size a lot, but most of these are quite useful as > soon as you get used to them. Most of them can be applied automatically using Eclipse (e.g. diamonds). Multi-catch is very useful. Also

Re: Java 6 support

already moved to JDK 1.7 [1] - so this should be ok for them. So I'm "0" on this issue. Andi. [1] https://issues.apache.org/jira/browse/TIKA-1536 -- View this message in context: http://apache-poi.1045710.n5.nabble.com/Java-6-support-tp5721373p5721374.html Sent from the POI - Dev ma