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,
--
Yeah sure. I will upload in github and let you know
On Sat, 18 May 2019 at 9:54 PM, Parichay Barpanda <
parichay.barpa...@gmail.com> wrote:
> 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
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.
On Sat 18 May, 2019,
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.
On Sat, 18 May 2019 at 9:35
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
I don’t quite get it. Can you describe the real world scenario you’re trying to
implement?
Best,
Jeff
Sent from my iPhone
> On May 18, 2019, at 8:07 AM, selva vignesh wrote:
>
> Hi Adrien,
> Thanks for replying.. my question is if I want to install my plugin it should
> ask me to mentioned
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
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
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
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this
