Re: plugin maven groupId
Ahh... makes sense. - Original Message - From: jenkinsci-dev@googlegroups.com To: jenkinsci-dev@googlegroups.com At: Jun 3 2013 13:41:17 On 06/03/2013 01:27 PM, Kevin Fleming (BLOOMBERG/ 731 LEXIN) wrote: > Any configuration data persisted under the old class names would need to be > converted, though, right? I was not suggesting changing package/class names. -- 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. For more options, visit https://groups.google.com/groups/opt_out. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: plugin maven groupId
On 06/03/2013 01:27 PM, Kevin Fleming (BLOOMBERG/ 731 LEXIN) wrote: Any configuration data persisted under the old class names would need to be converted, though, right? I was not suggesting changing package/class names. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: plugin maven groupId
Any configuration data persisted under the old class names would need to be converted, though, right? The EC2 plugin has an example of migrating data from an old class name to a new one (EC2Cloud -> AmazonEC2Cloud), if that is useful. - Original Message - From: jenkinsci-dev@googlegroups.com To: jenkinsci-dev@googlegroups.com At: Jun 3 2013 12:45:17 On 06/03/2013 12:24 PM, James Nord (jnord) wrote: > The plugin is still using the old org.jvnet.hudson.plugins Maven groupId – so > I was considering changing this at the same time. > > However I wasn’t sure if this is required to stay the same for plugin updates > (or any other reason). Plugin updates only consider the artifactId, so if you are dropping Hudson compatibility then you can and should switch to org.jenkins-ci.plugins for the groupId (which will be the default when you use the Jenkins plugin parent POM). -- 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. For more options, visit https://groups.google.com/groups/opt_out. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: plugin maven groupId
On 06/03/2013 12:24 PM, James Nord (jnord) wrote: The plugin is still using the old org.jvnet.hudson.plugins Maven groupId – so I was considering changing this at the same time. However I wasn’t sure if this is required to stay the same for plugin updates (or any other reason). Plugin updates only consider the artifactId, so if you are dropping Hudson compatibility then you can and should switch to org.jenkins-ci.plugins for the groupId (which will be the default when you use the Jenkins plugin parent POM). -- 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. For more options, visit https://groups.google.com/groups/opt_out.
plugin maven groupId
Hi all, I am biting the bullet and dropping support for Hudson from my plugin (the Hudson community have forked it anyway). The plugin is still using the old org.jvnet.hudson.plugins Maven groupId - so I was considering changing this at the same time. However I wasn't sure if this is required to stay the same for plugin updates (or any other reason). So before I make the change to the groupId is there any reason not to? /James -- 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. For more options, visit https://groups.google.com/groups/opt_out.
