You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
This is a regression from Jakarta EE 8 (possibly 9)
Platform API JARs should not include the Spec JARs as transitive dependencies, as seen below.
The leads to duplicate classes on the classpath and problems
if an application uses has JPMS module-info anywhere (split package issues)
Possible Solution
I think you can make the Spic JARs <optional>true</optional> to solve this problem
Currently, it is set to false, not sure what's the reason for that.
The text was updated successfully, but these errors were encountered:
Describe the bug
This is a regression from Jakarta EE 8 (possibly 9)
Platform API JARs should not include the Spec JARs as transitive dependencies, as seen below.
The leads to duplicate classes on the classpath and problems
if an application uses has JPMS
module-info
anywhere (split package issues)To Reproduce
Steps to reproduce the behavior:
Workaround
The issue can be worked around by excluding all transitive dependencies:
Possible Solution
I think you can make the Spic JARs
<optional>true</optional>
to solve this problemCurrently, it is set to false, not sure what's the reason for that.
The text was updated successfully, but these errors were encountered: