Plugin hosting request

[dcar...@redhat.com]

Hi!

I've just created a new plugin and I'd like to have it hosted on your infra so it's easy to install/follow from jenkins itself.


The plugin is the Jython Postbuild Plugin, right now located at:

 https://github.com/david-caro/jython-postbuild-plugin


My github account is david-caro.


Thanks!


pd. I also plan on greating a jython plugin, similar to groovy plugin, so if you create also that repo I'd be grrateful, if not, I'll ask again once I have a personal repo with some code.

[Kanstantsin Shautsou]

Why hudson in <groupId>org.dcaro.hudson.plugins</groupId> ?

[David Caro]

On 12/04, Kanstantsin Shautsou wrote:
> Why hudson in <groupId>org.dcaro.hudson.plugins</groupId> ?

Why not?

I just replaced the jvnet entries from the groovy post build plugin for
dcaro.

I'm not very familiar with java programming or package organization,
so any input is welcome. But afaik that's not an issue and will ler me
create other plugins using the same subpackage (hudson), am I right?

> --
> You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/ma5PzBlMbWE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4ff6dd4a-2230-4125-8f3d-b046793031a9%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.


--
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D

Tel.: +420 532 294 605
Email: dc...@redhat.com
Web: www.redhat.com
RHT Global #: 82-62605

[Vojtech Juranek]

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

[Daniel Beck]

On 05.12.2014, at 13:08, Vojtech Juranek <vjur...@redhat.com> wrote:

> 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.

Package names (for code/data compatibility) and artifact ID (used by update center; to allow upgrading, prevent duplication) matter, but what is Maven group ID used for?