Great idea! I rejected PRs attempting to modify their path before. I submitted https://github.com/jenkins-infra/repository-permissions-updater/pull/3047 to make it obvious that altering specific components is highly discouraged.
On Wednesday, 21 December 2022 at 17:45:20 UTC+1 jgl...@cloudbees.com wrote: > On Sun, Dec 18, 2022 at 7:47 AM Alexander Brandes <mc.ca...@gmail.com> > wrote: > >> take a look at the RPU documentation >> <https://github.com/jenkins-infra/repository-permissions-updater/#renaming-a-plugin> >> how >> to do that. >> > > I think this doc should be made to emphasize that you *really really* > should not ever do this unless you are pretty sure your plugin has no users > under its existing name. > > Changing the `name` (display name) is fine at any time. Changing the > `groupId` will break any Maven dependencies from other plugins, which may > or may not be an issue. But changing the `artifactId` means changing the > identifier by which the Jenkins plugin manager differentiates this plugin > from others, and will cause mayhem for users who have already installed it > under the old name. > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/c39e5c9e-6db8-4e62-a967-a7a1b8b041d8n%40googlegroups.com.
