New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Class collision between old jaxb2-basics-runtime and new one #465
Comments
New project to handle this : https://github.com/laurentschoelens/jaxb2-basics-empty |
laurentschoelens
added a commit
to laurentschoelens/jaxb-tools
that referenced
this issue
Apr 18, 2024
Include empty like project (same as above) in main branch so we can then include it in v2.x |
Adding the following in <dependency>
<groupId>org.jvnet.jaxb2_commons</groupId>
<artifactId>jaxb2-basics-runtime</artifactId>
<version>[4.0.0,9999.0)</version>
</dependency> and having a project including 2 projects, one with old runtime and one with new runtime as dependencies, result in the following
|
laurentschoelens
added a commit
to laurentschoelens/jaxb-tools
that referenced
this issue
Apr 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have same classes in same packages in both jaxb2-basics-runtime (the one with previous groupId and the one with the current one).
Since groupId differs, having the new one does not override the older one and it can leads to ClassCastException if all the classes are not loaded from the same jar.
We should provide a way to override the older one with maybe like an empty jar with older groupId to make sure all classes are defined only once
The text was updated successfully, but these errors were encountered: