-
Notifications
You must be signed in to change notification settings - Fork 56
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
Manifest Class-Path header not transformed #573
Comments
We are going to need a lot more details on the problem here to better understand the situation. Can you please provide a reproduction of the problem? |
When I create a jar, manifest is created as below Manifest-Version: 1.0 With the transformer, the javax reference in Cass-path of Manifest file is not changed, though the javax reference available inside the source class files are changed. plug-in definition: |
Thanks for the explanation. Transformer does not do anything with the Class-Path manifest header since it references things outside of the jar. The ManifestActionImpl only processes select manifest headers for package name changes. Lines 141 to 142 in 7b215ab
So for this case, you will need to modify the Class-Path manifest entry in some other way. |
With jakartaDefaults rules set to true the manifest of the jar is not changed. It still have references to javax
The text was updated successfully, but these errors were encountered: