Skip to content

Publish a multi-release JAR #25

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

Closed
wrandelshofer opened this issue Nov 17, 2022 · 2 comments
Closed

Publish a multi-release JAR #25

wrandelshofer opened this issue Nov 17, 2022 · 2 comments

Comments

@wrandelshofer
Copy link
Owner

"We use your java8 code in jackson-core. If you publish a jar with your java8 branch code that would be great - we would change our build to use your published jars and that shades the class packages to include them in jackson-core jar.

One solution would be to append '-java8' to the artifact name (and '-java17' for the java17 jar). Or maven supports 'classifiers' which basically lead to a similar result."

Originally posted by @pjfanning in #22 (comment)

@wrandelshofer
Copy link
Owner Author

Class shading does not work with modular Java anymore: if two modular Jar files contain the same package, the JVM refuses to start.

So, maybe, I should build a modular multi-release JAR?

This would allow to deploy a single JAR file that contains all the various code variants that we currently have in the java8, java11, java... branches.

@wrandelshofer
Copy link
Owner Author

The code in the dev branch now builds a multi-release jar.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant