-
Notifications
You must be signed in to change notification settings - Fork 121
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
Library cannot be used with Java Modules #286
Comments
Any thoughts on how to do this in a backwards compatible way? It's not essential to maintain compatibility, but if it is possible then it would be good to do so. |
Hi Richard, You could release separate artifacts for Java9+ like guava originally did (they did it for Java8 support) and eventually turn that into the default in the next major release. With that approach you'd need to break compatibility eventually. Another thing you could do is merge the JAR files so there is only one exporting the package and the other is empty. Maybe someone has a third idea :) In our own product, we opted to just break compatibility. |
Hey @RichardWarburton, Did you decide how to proceed? |
This was perceived to be a low priority item by clients so I've not progressed it. |
This library cannot be used with Java Modules because it exports the same package from multiple JAR files.
uk.co.real-logic:artio-core:0.31
anduk.co.real-logic:artio-codecs:0.31
export packageuk.co.real_logic.artio
uk.co.real-logic:artio-core:0.31
dependson uk.co.real-logic:artio-codecs:0.31
so one cannot importuk.co.real-logic:artio-core:0.31
Proposed fix: Move the classes into different package so that each JAR exports a unique package name.
The text was updated successfully, but these errors were encountered: