chore: Remove developers
tag from pom.xml
#394
Merged
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
jobcacher
developers! 👋This is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipe to modernize the plugin:
Remove developers tag
io.jenkins.tools.pluginmodernizer.RemoveDevelopersTag
Why is this important?
Removing
developers
Tag frompom.xml
Jenkins no longer requires the
developers
tag inpom.xml
since thedevelopers
section in the pom.xml file was traditionally used to specify individuals responsible for the plugin.However, Jenkins has transitioned to using the Repository Permission Updater (RPU) for managing permissions and developer information.
Benefits of Removing
developers
Tag:By removing the
developers
tag, we adhere to the modern Jenkins infrastructure standards and prevent the inclusion of outdated or redundant developer information in plugin metadata.