Betreff: Re: [fileupload] jakarta versus javax?
Le jeu. 31 mars 2022 à 18:58, Bernd Eckenfels a
écrit :
> Why not just rename the few dependency classes to their proper name
> manually and release a new major branch? That could even be contributed by
> any of the people asking fo
ucau
> Gesendet: Thursday, March 31, 2022 8:54:05 AM
> An: Commons Developers List
> Betreff: Re: [fileupload] jakarta versus javax?
>
> AFAIK there are two mains options:
>
> 1. relocation (shade plugin which is used a lot for impacted projects or
> alike)
> 2. a bridge sin
Gesendet: Thursday, March 31, 2022 8:54:05 AM
An: Commons Developers List
Betreff: Re: [fileupload] jakarta versus javax?
AFAIK there are two mains options:
1. relocation (shade plugin which is used a lot for impacted projects or
alike)
2. a bridge since API is close enough to use one and wire
AFAIK there are two mains options:
1. relocation (shade plugin which is used a lot for impacted projects or
alike)
2. a bridge since API is close enough to use one and wire to the other
(like
https://github.com/yupiik/uship/tree/master/servlet-jakarta-javax-bridge)
Advantage of 1 is to only
With PrimeFaces we use a special plug-in for Shade that builds a second jar
that renames javax to Jakarta everywhere and in maven central it adds the
Jakarta classifier to the jar so we can have both javax and Jakarta versions
built from the same code base.
See:
That would probably need to be a major release as it would break backwards
compatibility for other consumers.
I don't know the roadmap for fileupload but I would suggest raising a jira
ticket for this new feature request.
Looking at Tomcat 10.x it appears to be Servlet 5.0 specification which is
Just now joining this list. I've installed Tomcat 10.0.17 which uses the
jakarta class, not javax. FileUpload 1.4 (the most recent as far as I
can tell) uses javax. Is FileUpload schedule for a new version using
jakarta?
Thanks --Mark