Thanks. Unfortunately, the artifactId contains "ibm", so I would like to change that, as well. That's an interesting idea regarding having the new plugin depend on the old one. I'll look into that.
On Wednesday, October 9, 2019 at 9:44:25 AM UTC-4, Daniel Beck wrote: > > > > > On 8. Oct 2019, at 19:01, Matt Murphy <[email protected] <javascript:>> > wrote: > > > > I tried searching for steps to accomplish this, but I haven’t found > anything. Is it possible to rename a plugin (including changing the > groupId)? > > Group ID can be changed, just need an update of the permissions YAML file. > Display name can be changed arbitrarily. Artifact ID is the difficult one. > If you change that, it's considered a different plugin, so your users will > need to migrate. > > You might be able to make it easier by moving actual code over to the new > plugin, adding a dependency to the new plugin from the (now gutted) old > plugin, and then users *should* get the migration mostly for free. Add an > admin monitor informing them that the old plugin can now be removed, and > done. > > This is not a particularly well-travelled path though, so there may be > unexpected problems, and it might be easier to just live with the with the > old artifact ID. Older components in the Pipeline plugins suite still have > the ca. pre-2015 'workflow-' prefix. > > -- 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/caabe870-71ce-4a6b-ada8-e8b9dc43703f%40googlegroups.com.
