Hello,
We do use POI with Java 8. We deploy to customer environments where we don’t
have a strong say in the runtime version. We do NOT think POI needs to support
Java 8 in the next version.
Cheers,
Marius
> On Feb 25, 2024, at 08:03, Dominik Stadler
> wrote:
>
> So I see two +1 and one
So I see two +1 and one -1 from comitters, one user stated a +1 for
updating support to Java 11+ in the next major version of Apache POI.
Unfortunately still not a very decisive outcome :(
So let's ask another way:
*Are you using Apache POI with Java 8 and do you think that it needs to
That commit does not affect what I was talking about. The issue I was talking
about is the
* cost in compiling and generating the poi-ooxml-full code - code that does not
change
* the major cost in building poi-ooxml-lite - again code that rarely changes -
but to build it you need to run all
@PJ:
Hi,
I just ran a poi-ooxml build and then ran the tests using the profiler. I made
a little code change (r1915953), and the profiler tells me it’s beneficial. I’m
still a bit sceptic, can you verify the tests run faster now? Maybe that’s
something I can improve on in the coming days.
I feel really bad that I mixed up versions when I asked this. POI 5 can of
course stay on Java 8 and everybody can be using POI 5 for as long as they
want. With Java 11 having reached Premier Support EOL in September last year,
we should be really having this conversation about Java 17 for POI
These are great points.
> On Feb 21, 2024, at 11:27 AM, PJ Fanning wrote:
>
> Usually when projects dump Java 8 support, they is a strong reason. I don't
> see any here.
> * I am not aware of any dependency that we rely on that has fixes that we
> can't uptake if we stick to Java 8 - ie the
Usually when projects dump Java 8 support, they is a strong reason. I don't see
any here.
* I am not aware of any dependency that we rely on that has fixes that we can't
uptake if we stick to Java 8 - ie the projects still publish Java 8 friendly
releases even if they have higher version
something to consider, which kind of gathers a few of the opinions that have
been discussed, maybe in a different light.
POI is in an odd situation because it is BOTH a consumer of dependencies, and
IS also a dependency, since it is a library and not a stand-alone product.
as a consumer of
Hi,
+1 for moving to Java 11 as minimum
My opinion is that we should jump to the oldest LTS version each time one LTS
reached its end of life. This means that we would jump from 8 to 17 at once...
Which is also not so friendly to be done right now!
Kind regards,
Alain FAGOT BÉAREZ
Obter
Hi,
What do others thing?
We currently are at +2/-1 for moving to Java 11 minimum.
Would be good if we get a more significant number of votes for this.
Thanks... Dominik.
On Sat, Feb 3, 2024 at 10:04 PM Axel Howind wrote:
> Hi,
>
> for whatever reason I cannot reach both the Nabble and
+1 from me of course, since I suggested the switch.
> Am 03.02.2024 um 22:04 schrieb Axel Howind :
>
> Hi,
>
> for whatever reason I cannot reach both the Nabble and MarkMail archives to
> check if this has been discussed before, but I think it would be a good idea
> to bump the minimum Java
Hi,
+1 from me for raising minimum Java to 11
* We can get rid of some build-complexity
* Anybody who is at Java 8 should start planning upgrading by now in my
opinion
* expected performance improvements seen when upgrading are sometimes
impressive and make for a very easy business
A minimum Java version usually means that a project will not work with older
Java versions. So if XMLBeans requires Java 8, that would mean we should be
fine in having POI using at least Java 11. Even if there would be any
incompatibility, we could fix these issues in XMLBeans ourselves.
Since
I certainly know since I helped negotiate it out of the Apache Attic.
My point is that XMLBeans remains a separate codebase and build from POI. If it
requires Java 8 then POI requires Java 8. What java version does XMLBeans
require?
> On Feb 4, 2024, at 12:04 PM, Axel Howind wrote:
>
> AFAIK
AFAIK XMLBeans is now maintained by the POI project itself, so it should not be
problematic.
> Am 04.02.2024 um 20:59 schrieb Dave Fisher :
>
> What version of Java is the minimum for XMLBeans? We should not forget
> XMLBeans in this discussion.
>
> Best,
> Dave
>
>> On Feb 3, 2024, at 5:54
What version of Java is the minimum for XMLBeans? We should not forget XMLBeans
in this discussion.
Best,
Dave
> On Feb 3, 2024, at 5:54 PM, Axel Howind wrote:
>
> No one forces users of POI to update to the latest version. Going to 11 in
> POI 6 doesn't mean we
> have to stop providing bug
No one forces users of POI to update to the latest version. Going to 11 in POI
6 doesn't mean we
have to stop providing bug fixes to POI 5 from one day to the next. But whoever
is still using
Java 8 is now certainly used to not being able to use the newest version of
every dependency.
Most
that may very well be, BUT, many commercial shops are migrating apps from 8 and
11 where able because the blood money for EoL java is starting to be a tax they
don't want to pay if possible. just like when we had to bite the bullet with
1.1, 1.5 and 1.8, i recommend at the very least, moving
Current POI version is 5.2.5. So I presume the idea is to release a POI 6 with
Java 11 only support. I'm -1 on this. I don't see any great advantage in only
supporting Java 11. Java 8 is still widely supported by vendors.
https://endoflife.date/oracle-jdk says 6 more years of Java 8.
On
Hi,
for whatever reason I cannot reach both the Nabble and MarkMail archives to
check if this has been discussed before, but I think it would be a good idea to
bump the minimum Java version for POI 5 to 11. I’d also be ok (or rather like)
17. What do you think?
Cheers,
Axel
20 matches
Mail list logo
