+1 on requiring Java 11... no problem there.
Can you clarify what exactly "require jakarta" means? Tika will link to
dependencies that happen use jakarta package names, but will have no
problem running in a javax container (such as Tomcat 9.0.x) with javax
libraries present? Or something else?
Thanks,
Adam
On 9/12/2023 9:11 PM, Luís Filipe Nassif wrote:
+1 from our side, we moved to java 11 last year.
Best,
Luis
Em ter, 12 de set de 2023 19:01, Ken Krugler
<kkrugler_li...@transpac.com> escreveu:
+1
On Sep 12, 2023, at 7:56 AM, Tim Allison <talli...@apache.org> wrote:
Sorry, let me try that again.
The proposal:
1) start parallel main (3.x) and branch_2x branches now.
2) cut a first release of 3.0.0 by the end of September (maybe
October) of 2023
3) Set the EOL for the 2.x branch one year after the first
release of 3.0.0 -- possibly set 2.x to "security fixes only" 6
months after the first release of 3.0.0?
In 3.x, we'd require Java 11 and jakarta. We wouldn't make many
other major changes.
On Tue, Sep 12, 2023 at 10:49 AM Tim Allison
<talli...@apache.org> wrote:
>If Tika users will be happy to move on and drop Java 8
and/or javax. Please drop them :)))
Fellow devs and broader Tika community, are we ok with
EOL'ing Tika 2.x and dropping support for Java 8 and javax in
September 2024?
--------------------------
Ken Krugler
http://www.scaleunlimited.com
Custom big data solutions
Flink, Pinot, Solr, Elasticsearch
