Plugin name, Id change

[fkp...@gmail.com]

Hi,
Due to some re-branding issues - we need to change the name of the plugin.
As far as I know -  I can simply change the POM file. but -

1. What else should i take into consideration? Change?
2. which steps should I take prior to POM change?
3. How will it effect The Jira, WIKI and Jenkins plugin stats?

If anyone had any experience with this and can spare me the "try and fail" around this - I'd be happy to hear!

Thanks ahead...

[Baptiste Mathus]

Hello,

Basically, "renaming" a plugin ID does not exist. By that I mean that if you change the artifactId, it's equivalent to create a new plugin. Users won't be able to upgrade. Your stats will restart from 0, and so on. 

You can possibly just adjust the name tag in your pom.xml. It will be visible to end users (after release).

HTH 

Cheers

--
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 jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e2949554-d418-4a19-9b78-853d3fd7c6ec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[fkp...@gmail.com]

Thanks!
How about changing the repository name?
It will require a change on jenkinsci....

More of that - will the Jenkins wiki link change if we change only the name?

On Sunday, January 1, 2017 at 11:13:23 AM UTC+2, Baptiste Mathus wrote:

Hello,

Basically, "renaming" a plugin ID does not exist. By that I mean that if you change the artifactId, it's equivalent to create a new plugin. Users won't be able to upgrade. Your stats will restart from 0, and so on. 

You can possibly just adjust the name tag in your pom.xml. It will be visible to end users (after release).

HTH 

Cheers

Le 1 janv. 2017 8:08 AM, <fkp...@gmail.com> a écrit :

Hi,
Due to some re-branding issues - we need to change the name of the plugin.
As far as I know -  I can simply change the POM file. but -

1. What else should i take into consideration? Change?
2. which steps should I take prior to POM change?
3. How will it effect The Jira, WIKI and Jenkins plugin stats?

If anyone had any experience with this and can spare me the "try and fail" around this - I'd be happy to hear!

Thanks ahead...

--
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 jenkinsci-de...@googlegroups.com.

[Daniel Beck]

> On 01.01.2017, at 18:16, fkp...@gmail.com wrote:
>
> How about changing the repository name?
> It will require a change on jenkinsci....

By convention, repo names match artifactId with possibly a -plugin suffix. Some exceptions exist, e.g. multi-project repos, but those are rare.

> More of that - will the Jenkins wiki link change if we change only the name?

No, two plugins can link to the same wiki page, but the macro on the wiki page will need to specify an artifactId for which data is shown.

But you can of course rename the wiki page, as long as the current release of the plugin references the correct wiki page name, which is an automatically enforced prerequisite to be published. So that needs to be coordinated.

[Martin Weber]

Am Samstag, 31. Dezember 2016, 23:08:45 schrieb fkp...@gmail.com:
> Hi,
> Due to some re-branding issues - we need to change the name of the plugin.

I renamed the cmakebuilder plugin in 2016. You might want to look at the
change history of its pom and the wiki page [1] as a guide.

Martin

[1] https://wiki.jenkins-ci.org/display/JENKINS/cmakebuilder+Plugin

--
Cd wrttn wtht vwls s mch trsr.

[fkp...@gmail.com]

Hi,
I've continued the research on this - and why didn't you change the repository name?
It's possible by the organization authorization - or it was disabled at that time?

[Martin Weber]

Am Samstag, 21. Januar 2017, 22:00:53 schrieb fkp...@gmail.com:
> Hi,
> I've continued the research on this - and why didn't you change the
> repository name?

Do you mean the plugins´ artifact-ID in the repository?
It will loose the plugins´ installation statistics and you will loose all
users that have the plugin already installed: There will have to reinstall the
plugin with its new name, there is no way to auto-update to the new-named
plugin.

Martin

> It's possible by the organization authorization - or it was disabled at
> that time?
>
> On Sunday, January 1, 2017 at 9:16:25 PM UTC+2, Martin Weber wrote:
> > Am Samstag, 31. Dezember 2016, 23:08:45 schrieb fkp...@gmail.com
> >

> > <javascript:>: