Deprecate integration with analysis-core #251
Merged
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
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.
See JENKINS-55744. The Static Analysis Utilities (
analysis-core) plugin has been marked as end-of-life, and the relevant functionality has been integrated into the Warnings Next Generation Plugin (warnings-ng) plugin. At some point we will need to drop support foranalysis-coreintegration fromemail-ext, ideally afteremail-extgains integration withwarnings-ng(pull requests welcome!) to avoid dropping this functionality. This change announces the deprecation to users, directing them to the Jira issue for any further discussion. This way, there will be no surprises when it comes time to drop support foranalysis-coreintegration fromemail-ext.