On Wed, 18 Mar 2015 12:08:37 +0100, Bruno <[email protected]>
wrote:
But I still have the @Extension in my Publisher class. How does it work
altogether ? I thought that the @Extension was kind of the door for
Jenkins
to enter the plugin.
@Extension is just an annotation Jenkins uses to auto-discover your
implementations of ExtensionPoint. You can have any number of
ExtensionPoint implementations in your plugin and therefore any number of
@Extension annotations.
Mixing the persistence of two unrelated classes together in obviously a
bad idea.
--
oliver
--
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/op.xvoxk4dosbfict%40localhost.localdomain.
For more options, visit https://groups.google.com/d/optout.
