poi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Woolsey <greg.wool...@gmail.com>
Subject Re: POI 4.0 and Java 8
Date Mon, 28 Aug 2017 21:14:07 GMT
Vaadin is Java 8.

On Mon, Aug 28, 2017, 13:48 Javen O'Neal <javenoneal@gmail.com> wrote:

> Other stakeholders we should ping?
>
> > Vaadin, if they're on Java 6 or 7.
>
> On Aug 28, 2017 8:50 AM, "Allison, Timothy B." <tallison@mitre.org> wrote:
>
> Thank you, David!
>
> Anyone with contacts at/works for Alfresco?
>
> Other stakeholders we should ping?
>
> From: David Pilato [mailto:david@pilato.fr]
> Sent: Monday, August 28, 2017 10:27 AM
> To: dev@tika.apache.org; Allison, Timothy B. <tallison@mitre.org>
> Cc: POI Developers List <dev@poi.apache.org>
> Subject: RE: POI 4.0 and Java 8
>
> Nope. Elasticsearch does not support 1.7 anymore in 5.x, 6.x and master
> branch.
>
> +1 to switch to 1.8.
>
> --
> David Pilato, elastic.co
> Developer | Evangelist, [X]
>
> Le 28 août 2017 à 15:14 +0200, Allison, Timothy B. <tallison@mitre.org
> <mailto:tallison@mitre.org>>, a écrit :
>
> +1 from me.
>
> David, any problems with ES if Tika migrates to jdk8?
>
> -----Original Message-----
> From: Konstantin Gribov [mailto:grossws@gmail.com]
> Sent: Wednesday, August 23, 2017 1:11 PM
> To: dev@tika.apache.org<mailto:dev@tika.apache.org>
> Cc: POI Developers List <dev@poi.apache.org
> Subject: Re: POI 4.0 and Java 8
>
> Hi, folks.
>
> IIRC we moved to jdk7 somewhere around 1.9-1.10. Primary issue was not to
> break downstream libraries and projects of course. Same as before we will
> have to make at least two releases after decision about such a migration
> (to announce java 7 support deprecation in first release and migrate on
> next one).
>
> Since Oracle jdk7 get EOL status in 2015, it seems ok to migrate to jdk8 to
> me. We originally discussed it as a minor goal for 2.x but its release time
> frame isn't clear and, I guess, wouldn't be clear in next several months at
> least.
>
> I'd like to know what other PMCs & devs could say about downstream projects
> and migration. Apache Solr requires 1.8 since 6.0 (Apr 2016), so it
> wouldn't be an issue to them. Maybe someone could shed some light on other
> downstream who isn't on jdk8 yet.
>
> If there's no blockers for that I'm +1 for migrate to java 8.
>
>
> On Wed, Aug 23, 2017 at 1:10 AM Andreas Beeker <kiwiwings@apache.org
> <mailto:
> dev@poi.apache.org%0bSubject:%20Re:%20POI%204.0%20and%
> 20Java%208%0b%0bHi,%20folks.%0b%0bIIRC%20we%20moved%20to%
> 20jdk7%20somewhere%20around%201.9-1.10.%20Primary%20issue%
> 20was%20not%20to%20break%20downstream%20libraries%20and%20projects%20of%
> 20course.%20Same%20as%20before%20we%20will%20have%20to%20make%20at%20least%
> 20two%20releases%20after%20decision%20about%20such%20a%
> 20migration%20(to%20announce%20java%207%20support%
>
> 20deprecation%20in%20first%20release%20and%20migrate%20on%20next%20one).%0b%
> 0bSince%20Oracle%20jdk7%20get%20EOL%20status%20in%202015,%
> 20it%20seems%20ok%20to%20migrate%20to%20jdk8%20to%20me.%20We%20originally%
> 20discussed%20it%20as%20a%20minor%20goal%20for%202.x%
> 20but%20its%20release%20time%20frame%20isn't%20clear%20and,
> %20I%20guess,%20wouldn't%20be%20clear%20in%20next%20several%
> 20months%20at%20least.%0b%0bI'd%20like%20to%20know%20what%
> 20other%20PMCs%20&%20devs%20could%20say%20about%
> 20downstream%20projects%20and%20migration.%20Apache%20Solr%
> 20requires%201.8%20since%206.0%20(Apr%202016),%20so%20it%
> 20wouldn't%20be%20an%20issue%20to%20them.%20Maybe%20someone%20could%20shed%
> 20some%20light%20on%20other%20downstream%20who%20isn't%
> 20on%20jdk8%20yet.%0b%0bIf%20there's%20no%20blockers%
> 20for%20that%20I'm%20+1%20for%20migrate%20to%20java%208.%0b%
> 0b%0bOn%20Wed,%20Aug%2023,%202017%20at%201:10%20AM%20Andreas%20Beeker%20%
> 3ckiwiwings@apache.org>> wrote:
>
>
> Hi Tika devs,
>
> at POI, we are about to have a major change in the upcoming version
> after POI 3.17 is out, which will be probably in the next week or so.
>
> Up till now we had a discussion [1], about the next Java SE, i.e. Java
> 7 or 8, and it looks like Java 8 is the preferred version - with the
> restriction on how you'll get along with that decision.
>
> In an ideal world you would say, ok we switch to Java 8 too, but I
> guess this won't happen ...
> at least not so fast.
>
> To continue the discussion, I could try to gather a few arguments why
> it would make sense to switch, but in the end you also have upstream
> dependencies to check for, e.g. elasticsearch [2].
>
> So I would choose a different approach...:
> - do you have any plans to switch to Java 8? when would that be?
> - if we decide to go on, how much of an impact would that be for Tika (...
> to rely on an older POI version)?
> - any recommendations? maybe something like a mixed versions jar
>
> Thank you,
> Andi
>
> [1]
> http://apache-poi.1045710.n5.nabble.com/Discussions-on-POI-4-0-Java7-8
> -voting-td5728560.html
> <http://apache-poi.1045710.n5.nabble.com/Discussions-on-POI-4-0-Java7-8-voting-td5728560.html>
> [2]
> https://www.elastic.co/guide/en/elasticsearch/reference/current/setup.
> html
> <https://www.elastic.co/guide/en/elasticsearch/reference/current/setup.html>
>
>
> --
>
> Best regards,
> Konstantin Gribov
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message