I think Robert is answering the 2/ point. Maven dependencies are actually the same. Jenkins typical packaging uses Maven. Adding a plugin as a dependency will package the plugin with the related plugin as required (or not if you use the optional tag).
As for the 1/ point. I think the only reasonable solution is to use the jenkins-cli with the groovy or groovysh commands. Cheers 2015-05-18 12:56 GMT+02:00 Gilad Baruchian <[email protected]>: > Thank you Robert! >> > I am assuming you are talking about maven dependencies, how do I add the > dependencies for a plugin? > > -- > 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/4c07456f-e0a9-4b05-b447-899cd586c3cb%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/4c07456f-e0a9-4b05-b447-899cd586c3cb%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- 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/CANWgJS59oeiEd%3DsH-PEtkv6xyWK2VZ%3D_j1W6ST6SMc3qW8S6Lw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
