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
The maven artifact deployed publicly is an shaded jar, which means it includes its dependencies directly in the jar as opposed to letting maven include them as dependencies. In Java 9+ projects that also include one of those dependencies, this causes a compilation error because the packages for those dependencies are available from two different modules -- yours and the actual dependency.
E.g., my project depends on both glisten-afterburner (which depends on this project) and indriya. Both depend on javax.inject, but because this project puts the package and classes for javax.inject directly into the jar, we run into this issue (this from a java 17 compile):
[ERROR] path/to/src/main/java/module-info.java: [1,1] module my.project.module reads package javax.inject from both javax.inject and afterburner.mfx
That is, split packages are no longer allowed.
Please deploy a version of this project's maven artifact that isn't a shaded jar!
The text was updated successfully, but these errors were encountered:
marinier
changed the title
Maven artifact for this project is an uber jar, which breaks modules
Maven artifact for this project is a shaded jar, which breaks modules
Aug 4, 2022
The maven artifact deployed publicly is an shaded jar, which means it includes its dependencies directly in the jar as opposed to letting maven include them as dependencies. In Java 9+ projects that also include one of those dependencies, this causes a compilation error because the packages for those dependencies are available from two different modules -- yours and the actual dependency.
E.g., my project depends on both glisten-afterburner (which depends on this project) and indriya. Both depend on javax.inject, but because this project puts the package and classes for javax.inject directly into the jar, we run into this issue (this from a java 17 compile):
That is, split packages are no longer allowed.
Please deploy a version of this project's maven artifact that isn't a shaded jar!
The text was updated successfully, but these errors were encountered: