On Friday, March 17, 2017 at 11:54:28 AM UTC-3, Jesse Glick wrote: > > On Fri, Mar 17, 2017 at 10:50 AM, Janario Oliveira > <[email protected] <javascript:>> wrote: > > I've renamed the artifactId of the plugin http_request to > > http-request-plugin. > > I would advise you revert that ASAP. > > First of all, there is no mechanism in Jenkins to change the ID of a > plugin after people have installed it. So users will not see an > upgrade; they will just see an unrelated plugin. > I understand that Jenkins doesn't change the ID. I added information on the last release before the rename It will show 2 plugins, the new one and the old one with information of rename
The reason I'm changing it is because the links and configuration points to a wrong destination e.g. https://plugins.jenkins.io/http_request Wrong: Github https://github.com/jenkinsci/http_request-plugin Jira http://issues.jenkins-ci.org/secure/IssueNavigator.jspa?mode=hide&reset=true&jqlQuery=project+%3D+JENKINS+AND+status+in+%28Open%2C+%22In+Progress%22%2C+Reopened%29+AND+component+%3D+%27http_request-plugin%27 Changes https://github.com/jenkinsci/http_request-plugin/compare/http_request-1.8.14...master And It goes in other places. If there is a way to fix all this, I could keep the old name > Second, the new name is wrong! Jenkins plugin names should not end in > `-plugin`. > I could use http-request > > So revert the name change, and if you managed to deploy an artifact > under the new name, file an INFRA ticket to get the bogus release > blocked from the update center before people get confused. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/7519fb14-ca49-4691-9da6-f4c514c21979%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
