https://bz.apache.org/bugzilla/show_bug.cgi?id=63555
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Mark Thomas <ma...@apache.org> ---
The feature that implements this in bnd isn't in a released version yet. There
are also a number of open questions:
- What requirements will Jakarta EE add around JPMS in future versions?
- If Tomcat provides a spec JAR (e.g. Servlet spec) should it use the same JPMS
name as the Jakarta EE provide JAR or a different one?
- How to handle the fact that some Tomcat JARs - e.g. bootstrap.jar - break the
packaging rules JPMS expects?
Given all of the above, I have added Automatic-Module-Name entries for all the
Tomcat controlled JARs in the embedded distribution but have deliberately not
added names for the other JARs to see how the above issues play out first.
This has been fixed in master for 9.0.23 onwards.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
