-
Bug
-
Resolution: Fixed
-
Minor
-
None
Looks like shillner is no longer maintaining the unleash-maven-plugin, see: https://github.com/shillner/unleash-maven-plugin/
So I think this Jenkins plug-in is also no longer maintained?
If so, it might be an idea to also add the "This plugin is up for adoption!" text to this plug-in so users know what they are getting into.
The unleash-maven-plugin does not work with Java 17 because the old Weld version it is using is incompatible. It will throw an exception which is fixed in newer versions, see: https://issues.redhat.com/browse/WELD-2572
So it is probably not a good idea for users to invest time in installing and using the plug-in when it has no future.
[JENKINS-70326] unleash-maven-plugin is no longer maintained, deprecate it
I've started the deprecation process with a pull request to the repository permissions updater. A pull request to the documentation archive is also needed and either a new topic on the plugin repository or a pull request to the update center repository.
Maybe Stanley is still around and can decide if it should be up for adoption or deprecated.
There is some helpful documentation on how to properly do this, see:
- https://www.jenkins.io/doc/developer/plugin-governance/deprecating-or-removing-plugin/
- https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/
OK thanks for your help markewaite . I only saw your comment after posting mine. 
The wiki archive is used for the plugin documentation. I've submitted the pull request to update the wiki docs archive so that we don't need to unarchive the Jenkins unleash plugin repository.
The "deprecated" topic has been added to the GitHub repository and the README in the GitHub repository has been updated to show that the Jenkins plugin is deprecated.
Thanks for reporting that. Since the Jenkins plugin repository has been archived and the Maven plugin repository has been archived, I think that plugin should be deprecated rather than listed as up for adoption. If someone wants to adopt the Jenkins plugin, the adopter would need to open the repository for write and would need to update the plugin.