chore: Upgrade to latest LTS core version supporting Java 8 (requires 2.346.3) #18
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
gounthar
force-pushed
the
plugin-modernizer/upgradetolatestjava8coreversion
branch
from
256d6c6 to
e848706
Compare
gounthar
changed the title
gounthar
force-pushed
the
plugin-modernizer/upgradetolatestjava8coreversion
branch
from
e848706 to
a6d357b
Compare
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.
Hello
hudson-wsclean-plugindevelopers! 👋This is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:
Upgrade to latest LTS core version supporting Java 8
io.jenkins.tools.pluginmodernizer.UpgradeToLatestJava8CoreVersion
Removing
developersTag frompom.xmlJenkins no longer requires the
developerstag inpom.xml, as thedeveloperssection was traditionally used to list individuals responsible for the plugin.Instead, Jenkins now uses the Repository Permission Updater (RPU) to manage permissions and developer information.
Benefits of Removing
developersTag:pom.xml, resulting in a cleaner and more maintainable file.Removing the
developerstag aligns with modern Jenkins infrastructure standards and prevents outdated or redundant developer information from being included in plugin metadata.