On Wed, Mar 25, 2015 at 12:38 PM, Ivo Bellin Salarin <[email protected]> wrote: > I must admit that the parametrized trigger is not a dependency of my plugin. > I've copied it in the plugins folder of my dev environment because it is > present in our production environment.
If you feel there is some possible or actual relationship to the code your plugin is running, add it as a <scope>test</scope> dependency. Then it will be loaded during functional tests as well as mvn hpi:run. -- 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/CANfRfr2Sb2A8n-qoZHTxVUsO3WHDx5aHh49aJdtCAy8pzzYrug%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
