On Wed, Dec 20, 2017 at 2:04 PM, Jochen Wiedmann <[email protected]> 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?
`@Extension` > Í 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. `GlobalConfiguration` -- 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/CANfRfr2v18CsB4SCq%3DR101WbY_9AhdQm7_%3DuEdwvzfQ%2B9hhoWA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
