Re: [Issue 328] Plugin cooperation

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: [Issue 328] Plugin cooperation

Kohsuke Kawaguchi-2
Eric Crahen wrote:
> It would be really great if we could literally include an example of this
> that could be checked out, built & installed in a Hudson instance.
> Especially for people who don't have time to try to comprehend maven.

OK. Will do.

>
> On 3/3/07, Kohsuke Kawaguchi <[hidden email]> wrote:
>>
>> Eric Crahen wrote:
>> > Can you show a simple example of how I would create a Maven project (A)
>> that
>> > has two artifacts - one being the Husdon plugin the second being the
>> classes
>> > I want to share.
>>
>> There are ways to make it work, but it's best to create one project for
>> the jar of classes, then create another project as a hudson plugin, as I
>> illustrated in http://hudson.dev.java.net/plugin-dependencies.html
>>
>> It's a bit more overhead, but I think it's easier than messing with POMs.
>>
>> > Then, without having to publish these artifacts, how I
>> > create a second project (B) which is a simple Hudson plugin that depends
>> on
>> > the second artifact I mentioned for project (A) ?
>>
>> --
>> Kohsuke Kawaguchi
>> Sun Microsystems                   [hidden email]
>>
>>
>
>

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [Issue 328] Plugin cooperation

Kohsuke Kawaguchi-2
Kohsuke Kawaguchi wrote:
> Eric Crahen wrote:
>> It would be really great if we could literally include an example of this
>> that could be checked out, built & installed in a Hudson instance.
>> Especially for people who don't have time to try to comprehend maven.
>
> OK. Will do.

I released maven-hpi-plugin 1.6, and with that the dependency handling
is simplified. There's no need to "create one project for ... then
another project as ..." like I said below.

Once again, the documentation is in
https://hudson.dev.java.net/plugin-dependency.html
and you can see this in action with the javanet-trigger-installer plugin
and the javanet-uploader plugin. Both are in Hudson CVS.


>
>>
>> On 3/3/07, Kohsuke Kawaguchi <[hidden email]> wrote:
>>>
>>> Eric Crahen wrote:
>>> > Can you show a simple example of how I would create a Maven project (A)
>>> that
>>> > has two artifacts - one being the Husdon plugin the second being the
>>> classes
>>> > I want to share.
>>>
>>> There are ways to make it work, but it's best to create one project for
>>> the jar of classes, then create another project as a hudson plugin, as I
>>> illustrated in http://hudson.dev.java.net/plugin-dependencies.html
>>>
>>> It's a bit more overhead, but I think it's easier than messing with POMs.
>>>
>>> > Then, without having to publish these artifacts, how I
>>> > create a second project (B) which is a simple Hudson plugin that depends
>>> on
>>> > the second artifact I mentioned for project (A) ?
>>>
>>> --
>>> Kohsuke Kawaguchi
>>> Sun Microsystems                   [hidden email]
>>>
>>>
>>
>>
>
>

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment