Dependency plugin specifier in Pom.xml

[selva vignesh]

HI,

  How to make some dependency plugin to be installed while our plugin before installing.
What are the changes need to be done at pom.xml.

Thanks in advance

[Adrien Lecharpentier]

Hello,

all you need is to declare the plugins as dependencies of your plugin. 

You need to specify them in `compile` scope and not optional. 

However, you should only declare those plugins if you need their code for your own plugin. 

From your question, I'm not sure it's the case.

BR,

-- Adrien

--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/f678a5d0-0ee5-4a76-b5f5-ed2b395bc674%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Adrien Lecharpentier

[selva vignesh]

Hi Adrien, 

Thanks for replying.. my question is if I want to install my plugin it should ask me to mentioned plugin should be installed example pipeline plugin should be installed first and after that only allow to install my plugin.  Or else installation must be failed and showing warning message as pipeline plugin install before install my plugin. 

Hope you understand now.. If not please let me know. I will explain again. 

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAKwJSvyFrXQFEfo_mCpvzZWiKc_rUZaz28r9Hx2mRg3S%2B0ACoQ%40mail.gmail.com.

[Jeff Pearce]

I don’t quite get it. Can you describe the real world scenario you’re trying to implement?

Best,

Jeff

Sent from my iPhone

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAOVVkp%3D9e_QYCutDYnVL3qq4SMtuia%2BGyKJPGAV57GWdumDHTA%40mail.gmail.com.

[selva vignesh]

For example if you install Jira plugin means it will install lot more plugins before it to be done. 

That’s the same scenario I want to do for some plugin. That’s what I am expecting. 

If you see in upgrademanager while installing jira plugin it will install 5 or 5 plugins like (workflow api) and all. 

Can you get it now ?

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/FC7C0AA5-276E-4A8A-8CAC-1D17758D682C%40gmail.com.

[Parichay Barpanda]

Hi Vignesh,

I am not quite sure I understand your problem but installing your dependency plugins before installing your plugin should be pretty straightforward:

1) Inside POM mention your dependency plugins within 'dependencies' tag

2) Run 'mvn clean install' then 'mvn hpi:run', your plugin should run a pseudo Jenkins instance with your plugin and it's dependencies installed.

Thanks,

Parichay (baymac)

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/FC7C0AA5-276E-4A8A-8CAC-1D17758D682C%40gmail.com.

[selva vignesh]

Hi Parichay, 

Yes I have tried. I have given build var plugin as a dependency and scope as compile time. 

While packaging using mvn package, it’s asking me do check commons-Lang 2.1 and Jenkins expecting 2.6. Can you please explain how Can I resolve this kind of issue. 

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAD0DWAP6nZQ0%3DNFTkN%3Duzqr3noNAMxLruUKrcMyQAcZiBK-ZAg%40mail.gmail.com.

[Parichay Barpanda]

I am not quite sure about this problem, maybe upgrade your Jenkins version to Jenkins LTS beyond 2.6 like 2.60.3.

And debugging on mailing list can be tedious and complicated. If you upload your plugin to GitHub or any other SCM and share the link I can take a look at it. 

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAOVVkp%3DXqvtKks%3D03d2aGya_F1wbYx-kz0%2BE4Uy5Szty41-KXQ%40mail.gmail.com.

[selva vignesh]

Yeah sure. I will upload in github and let you know

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAD0DWANPTpHd2krhF7opY164HBcxufdXywJb6y0ymgT3MJ8T7A%40mail.gmail.com.

[Adrien Lecharpentier]

What you are describing looks like an enforcer-rule report. 

It's there to let you know that your plugin depends on a older version of jenkins than what is required by one of your dependency. 

So yes, you need to update your `jenkins.version` to match what the dependency you added requires.

BR,

-- Adrien

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAOVVkpk_ySOJ1V9W_nXdVeDForgtfZvkRvRNZuzjTjzhEobm5A%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Adrien Lecharpentier