+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?
+1 from our side, we moved to java 11 last year.
Best,
Luis
Em ter, 12 de set de 2023 19:01, Ken Krugler
escreveu:
> +1
>
> On Sep 12, 2023, at 7:56 AM, Tim Allison wrote:
>
> Sorry, let me try that again.
>
> The proposal:
> 1) start parallel main (3.x) and branch_2x branches now.
> 2) cut a
Hello,
I am attempting to process some .msg files that have a considerable amount
of nested content that throw a "Suspected zip bomb: 100 levels of XML
element nesting" when using the out of the box HtmlParser +
EmbeddedContentHandler/BodyContentHandler on the body of the emails. Sadly
I am not ab
+1
> On Sep 12, 2023, at 7:56 AM, Tim Allison 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 a
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 on
The sooner, the better IMHO.
+1 to drop Java8 support.
David
--
David Pilato, elastic.co
Developer | Evangelist,
Le 12 sept. 2023 à 16:50 +0200, Tim Allison , a écrit :
> >If Tika users will be happy to move on and drop Java 8 and/or javax. Please
> >drop them :)))
>
> Fellow devs and broader
>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?
