Hi,
currently, we have already plugins availables on MarketPlace for SonarQube server.
We are working on our code source to rename our plugins : from “ecocode-" to "creedengo-”.
What is the process to do this renaming tacks for SonarQube Server MarketPlace ?
republish new plugins ? depreciate old plugins ? what are your best practices for this kind of work ?
Thank you.
David
Hi David,
I recommend you simply change the name that’s ‘published’ into the plugin jar’s manifest. That should update what we see in the Marketplace and the Plugin version matrix.
If you want to go further…
If you also change the plugin projects’ Maven Group and Artifact IDs, you’ll need to update the plugin properties files to change their default.mavenGroupId and default.mavenArtifactId values and add the old values to existing plugin version blocks. E.G. 1.1.0.mavenGroupId=io.ecocode and 1.1.0.mavenArtifactId=ecodocode-android-parent.
However, I don’t recommend changing the plugin keys. That will mean also renaming the properties files, and at that point, I don’t think the Marketplace will be able to track the change to recommend to your users to update from the old ecocode plugin version to the superceding creedengo plugin version.
HTH,
Ann
Hi @ganncamp
thank you for your feedback !
we want to delete all “ecocode” word references of our code for a legal concern about “ecocode” word.
what do you think if we create a new plugin with “creedengo” name (this is the new official name of our plugin) ?
Please see our french official communication about the renaming : ecoCode on LinkedIn: #numeriqueresponsable #greenit #opensource
thank you.
david
Hi @dedece35;
Thank you for your commitment to the green code collective.
Hi,
This would work. You run the risk of your users not picking up on the change & moving to the new plugin (which is what I was trying to avoid by suggesting you keep the technical key the same). But I suppose they’ll figure it out eventually?
Ann