On Wed, Dec 20, 2017 at 2:04 PM, Jochen Wiedmann
<[hidden email]> wrote:
> My plugin A is designed to provide an extension for an extension point,
> which is defined by plugin B (existing).
> - My understanding is, that I simply create a subclass of the extension
> point class, which in turn implements
> hudson.ExtensionPoint. No annotations, or something like that?
> Í assume, that I declare the jar files of B in my plugin as Maven
> dependencies with scope "provided", so that
> the necessary API is present at compile time.
No, use `compile` scope (i.e., do not specify `<scope>` at all).
> I'd like to configure my plugin with some config files location.
> How would I do that?
You would not.
> Preferrably without
> some UI, I am trying to keep things simple.
> On 20. Dec 2017, at 20:04, Jochen Wiedmann <[hidden email]> wrote:
> No annotations, or something like that?
https://jenkins.io/doc/developer/extensibility/ explains this and links to relevant Javadoc (the developer docs on jenkins.io are work in not-much-progress, but this is mostly covered -- and there are references to previous docs on the wiki for every topic we have docs on).