On Sun, Dec 18, 2022 at 7:47 AM Alexander Brandes <[email protected]> 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2eiZ%3DsKfcBBzdjpgmhQ3LMw0_N6o4y1Xum39J%3DCe890w%40mail.gmail.com.
