Work around ASM require upper bound dependencies error #916
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Apr 9, 2024
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Until ASM is removed from Jenkins core, we have a temporary situation where ASM is provided both by core (deprecated) and by the plugin system (in anticipation of the aforementioned removal), which can create Enforcer errors. Ignore these for now to avoid build spam until such a time that ASM is removed from core and widely deployed in an LTS release.
Testing done
Reproduced the problem described in the PR code comments in JaCoCo plugin by attempting to upgrade it to the latest BOM. Could no longer reproduce after these changes.
Fixes jenkinsci/bom#3098