maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anders Hammar <and...@hammar.net>
Subject Re: cargo:deploy fails to find artifact when run on parent project.
Date Wed, 16 Sep 2009 04:27:15 GMT
Yes. Was that a trick question? :-)
You just define that in the plugins element of the profile. I believe there
is something similar in the release profile that exists in the super pom.
Have a look at that or google.

/Anders

On Tue, Sep 15, 2009 at 22:40, James Russo <jr@halo3.net> wrote:

> Thanks. I found and read it. In my situation I really am doing it to just
> allow hudson to deploy it to the local "development" instance for others to
> test against. So that we always have a snapshot up and running we can poke
> at..
>
> What I have done is just added the cargo:deploy to the webapp pom and then
> just linked that goal to the deploy phase. so, now in hudson I go deploy and
> when it gets
> to that module (the webapp), it simply does the right thing and deploys it.
>
> Is there any way to include/exclude a plugin by specifying a profile? ex:
> can I have a hudson profile which attaches the cargo:deploy to the deploy
> phase so when calling deploy without that profile activated it won't attempt
> the cargo deploy?
>
> -jr
>
>
> Anders Hammar wrote:
>
>> There was a similar thread (however for glassfish) today. Have a look at
>> my
>> answer there about having a separate project for the deployment to
>> glassfish/tomcat.
>>
>> /Anders
>>
>> On Tue, Sep 15, 2009 at 21:18, James Russo <jr@halo3.net> wrote:
>>
>>
>>
>>> Hello,
>>>
>>>  I'm likely just not going this the right way.. Have a project with 5
>>> modules or so, one of which is a war. I'd like to be able to use
>>> cargo:deploy on the parent project and have it work to deploy the war.
>>> The
>>> problem is that it stops at my first module saying "artifact xyz isn't a
>>> dependency of common".. Which is true.
>>>
>>> The reason for this is I'd like to have hudson automatically deploy (via
>>> maven) the latest war to tomcat.  Seems like tomcat:deploy automatically
>>> skips modules where the artifact is not "war", not sure how I could
>>> achieve
>>> the same thing using cargo.
>>>
>>> -jr
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>>
>>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message