> > Which you can make those “6–12 projects” do. All they need to do is go > the plugin manager, uninstall the old plugin from *Installed* (which > will prompt to restart—but do not), then select the new plugin from > *Available* and *Download now and install after restart* and agree to > restart to apply changes. When it comes back up, it should have only > the correctly-named plugin installed, and the existing organization > folders should be loaded without incident (assuming, again, you did > not change package names or anything). >
Thank you, I renamed the packages back into their original name and it worked like a charm! I thought that all that mattered there was the plugin name AKA artifactId. > From what I understand, the old plugin was never on any update > center—it is being newly hosted, under the new and correct name. That is correct. AFAIK it's not yet on the update center, I think I had to do some tinkering first for that to work. Right now it's working with: The good plugin name -> *gitblit* The old package name -> *com.tsystems.sbs.gitblitbranchsource* It seems to me that this is not perfect, but at least the plugin name is correct and this would work for our projects. *Is the package name acceptable for you?* Many thanks Oleg and Jesse, your help is much appreciated :) -- 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/a599921e-c38f-4d8e-8eba-5f1a477a0471%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
