Hosting turbo plugin / Renaming
22 views
Skip to first unread message
Roman Stoffel
Oct 14, 2015, 11:45:24 AM10/14/15
to Jenkins Developers
Hello everybody
I would like to rename the 'SpoonScript Plugin'. From previous posts I think the procedure is to put up the plugin under the new name and then mark the old one as 'deprecated'.
The plugin is hosted here: https://github.com/turboapps/jenkins. However, previously that caused naming problems, so I've added a fork with a better name here: https://github.com/gamlerhart/turbo-script-plugin
The plugin is hosted here: https://github.com/turboapps/jenkins. However, previously that caused naming problems, so I've added a fork with a better name here: https://github.com/gamlerhart/turbo-script-plugin
All in all:
GitHub plugin name: turboscript
Jenkins Developer ID: gamlor
GitHub repository: https://github.com/turboapps/jenkins or https://github.com/gamlerhart/turbo-script-plugin
Thanks for your help.
GitHub plugin name: turboscript
Jenkins Developer ID: gamlor
GitHub repository: https://github.com/turboapps/jenkins or https://github.com/gamlerhart/turbo-script-plugin
Thanks for your help.
Christopher Orr
Oct 14, 2015, 1:50:44 PM10/14/15
to jenkin...@googlegroups.com
Hi there,
On 14/10/15 17:45, Roman Stoffel wrote:
> I would like to rename the 'SpoonScript Plugin'. From previous posts I
> think the procedure is to put up the plugin under the new name and then
> mark the old one as 'deprecated'.
That's more the procedure we have to go through when people needlessly
change their `artifactId` in their POM and make a release.
> The plugin is hosted here: https://github.com/turboapps/jenkins.
> However, previously that caused naming problems, so I've added a fork
> with a better name here: https://github.com/gamlerhart/turbo-script-plugin
It's not entirely clear to me what's going on here. I *guess* you work
with the original spoonscript-plugin author (pmateusz)? I don't think
we'd really want to deprecate any plugins without hearing from them
first.. :)
If you want to rename the plugin, the easiest thing to do isn't to
delete existing plugins and wiki pages and create everything again. You
can just update the `<name>` tag in the `pom.xml` file, rename the wiki
page, and update the `<url>` tag in your POM.
In this case the `artifactId` would remain as `spoonscript`, but this
isn't really user-visible within Jenkins. Plus that would allow
existing users to upgrade seamlessly to the renamed version.
Regards,
Chris
On 14/10/15 17:45, Roman Stoffel wrote:
> I would like to rename the 'SpoonScript Plugin'. From previous posts I
> think the procedure is to put up the plugin under the new name and then
> mark the old one as 'deprecated'.
change their `artifactId` in their POM and make a release.
> The plugin is hosted here: https://github.com/turboapps/jenkins.
> However, previously that caused naming problems, so I've added a fork
> with a better name here: https://github.com/gamlerhart/turbo-script-plugin
with the original spoonscript-plugin author (pmateusz)? I don't think
we'd really want to deprecate any plugins without hearing from them
first.. :)
If you want to rename the plugin, the easiest thing to do isn't to
delete existing plugins and wiki pages and create everything again. You
can just update the `<name>` tag in the `pom.xml` file, rename the wiki
page, and update the `<url>` tag in your POM.
In this case the `artifactId` would remain as `spoonscript`, but this
isn't really user-visible within Jenkins. Plus that would allow
existing users to upgrade seamlessly to the renamed version.
Regards,
Chris
Roman Stoffel
Oct 15, 2015, 1:25:56 PM10/15/15
to Jenkins Developers
Thanks Chris.
Ah cool. Mateusz and I will follow your advice and do it like this.
Ah cool. Mateusz and I will follow your advice and do it like this.
Reply all
Reply to author
Forward
0 new messages