On 2024/06/11 14:15:48 Rémy Maucherat wrote:
> Hi,
>
> To fix the issue with having Java 22 classes in tomcat-coyote (and
> embedded), I was looking at multi release JARs. I think it would work
> fine *if* we were building the JARs ourselves (jarIt task), but then
> the jars are actually rebuilt w
On 2024/06/11 14:15:48 Rémy Maucherat wrote:
> Hi,
>
> To fix the issue with having Java 22 classes in tomcat-coyote (and
> embedded), I was looking at multi release JARs. I think it would work
> fine *if* we were building the JARs ourselves (jarIt task), but then
> the jars are actually rebuilt w
My 2 cts would be to split anyway even if bnd can handle it:
* mjar can imply some classloading overhead
(java.util.jar.JarFile#getEntry) and keep the issue to have in a j17 jar >
17 bytecode (scanner not multirelease friendly will likely fail even if
tomcat shouldnt be scanned it stays scanned qu
Hi,
To fix the issue with having Java 22 classes in tomcat-coyote (and
embedded), I was looking at multi release JARs. I think it would work
fine *if* we were building the JARs ourselves (jarIt task), but then
the jars are actually rebuilt with bnd.
Supposedly bnd 7.0.0 (which we just upgraded to
