Hi Jesse,

I deleted the `maven-install-plugin` configuration.

And the standard jenkins plugin parent POM is already there.

I ran the following command (the additional params for groupid, artifactid, 
version are optional).:

mvn install:install-file 
-Dfile=/home/parichay/gsoc/gitlab-plugin/lib/gitlab-api.jar 
-DgroupId=io.jenkins.plugins -DartifactId=gitlab-api -Dversion=1.0-SNAPSHOT

Now I am able to depend on this plugin. I tried this before but really do 
not understand why this was failing. 

Let bygones be bygones.

Thanks for the help, now this definitely looks simpler than setting a NXRM 
server.

On Tuesday, April 16, 2019 at 6:53:03 AM UTC+5:30, Parichay Barpanda wrote:
>
> Hi jesse,
>
> Thanks for replying.
>
> Both are private plugins.
>
> Installing the plugin using the command as you have suggested is simple 
> enough but I couldn't make it work that way. It compiled successfully but I 
> was unable to import dependencies classes.
>
> I tried another method using the *maven install plugin*. What I did there 
> can be found here - 
> https://gist.github.com/baymac/6e822204da2c175d10933aedb893dd2a
> There was the same problem as installing the plugin from commandlline.
>
> I am confused if "installing the plugin" mean "installing the jar package 
> generated inside the */target* directory of the first plugin"?
>
> I will read your JEP when I have some time. 
>
> Regards,
> Parichay (baymac)
>
>
> On Mon 15 Apr, 2019, 18:39 Jesse Glick <[email protected] wrote:
>
>> On Sun, Apr 14, 2019 at 9:16 PM Parichay Barpanda
>> <[email protected]> wrote:
>> > I was working on 2 different plugins.
>>
>> Private plugins, or hosted in @jenkinsci?
>>
>> > The second plugin needed a way to depend on the first plugin. There 
>> were multiple ways it could be done like:
>>
>> This is quite routine for plugins hosted in the normal way. You do not
>> need to do anything special beyond declare the `<dependency>`. You can
>> even have dependencies on unreleased changes via JEP-305.
>>
>> > ii) Installing the jar in the local maven but for me it was a complex 
>> setup
>>
>> $ mvn -f first-plugin install
>>
>> is a complex setup?
>>
>> -- 
>> 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/CANfRfr2gM1b2HAo8aBpvaYd2OQA6ertuz5sLzesqwQx7dNmQ8w%40mail.gmail.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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/5c2be6c7-003a-4df3-9acb-aa288d2e9983%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to