Hi David, > > Why hudson in <groupId>org.dcaro.hudson.plugins</groupId> ? > > Why not?
it's up to you how you name the package, however, we prefer jenkins over hudson in package namespace, as hudson is now different project:-) Standard package name for new plugins is org.jenkinsci.plugins.$PLUGIN_NAME (org.dcaro.jenkins is also fine) > I just replaced the jvnet entries from the groovy post build plugin for > dcaro. well, some plugins have hudson package namespace because of backward compatibility. Job configs etc are serialized into XML and full class names (package name + class name) are used as XML elements, so if you rename a plugin, you can run into backward compatibility issues. HTH Vojta -- 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/2181821.TKBnxNg0DX%40localhost. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: This is a digitally signed message part.
