-
Notifications
You must be signed in to change notification settings - Fork 3
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
[24.2] "Duplicate name in Manifest" warnings on latest graal master builds #270
Comments
So far I'm not able to reproduce this locally. From CI the actual
Which come from the JDK, but that JDK code hasn't changed in years: So to me it looks like we see new warnings coming from the |
I don't know what I''m doing wrong, but locally this looks like this here:
i.e. CI has |
OK, so it looks to be local maven deploy and quarkus build with deployed maven artefacts from Deploying locally using
|
Interesting, so it looks like |
Something like that. I'll look into it more. |
graalvm/mx@bafad62 is the commit adding default |
So we ought to only add it/change it if there isn't any. Not blindly adding them again. |
Yes, or we can stop adding them in the |
I don't think we can do that, based on my understanding of this comment and since some checks also expect "Specification-Version" in source jars. The comment I think means the RHBQ rebuild's maven version of graal artefacts ought to match the maven version in the |
OK, finally managed to reproduce this with:
Interestingly it's the first time this new CI setup of deploying to local maven caught some issues. |
Previously, the build script would add these two attributes irrespective whether or not they'd exist in the Graal artefacts: Specification-Version Implementation-Version With this patch, only updates to the Implementation-Version attribute are done based on the maven version in use. Specification-Version is only added if it's not yet there in a jar or source jar file. Closes: Karm/mandrel-integration-tests#270
Previously, the build script would add these two attributes irrespective whether or not they'd exist in the Graal artefacts: Specification-Version Implementation-Version With this patch, only updates to the Implementation-Version attribute are done based on the maven version in use. Specification-Version is only added if it's not yet there in a jar or source jar file. Closes: Karm/mandrel-integration-tests#270 (cherry picked from commit 48c154e)
Previously, the build script would add these two attributes irrespective whether or not they'd exist in the Graal artefacts: Specification-Version Implementation-Version With this patch, only updates to the Implementation-Version attribute are done based on the maven version in use. Specification-Version is only added if it's not yet there in a jar or source jar file. Closes: Karm/mandrel-integration-tests#270 (cherry picked from commit 48c154e)
In our CI we see a couple of mandrel integration tests failing due to new warnings being printed:
It smells Quarkus related as those tests use the framework.
See: https://github.com/graalvm/mandrel/actions/runs/9866122260/job/27245030393
The text was updated successfully, but these errors were encountered: