exec:exec with "pom" artifact?

[Kristian Rink <ka...@zimmer428.net>]

Folks;

so far I make use of a "pom" artifact having several modules configured
in order to ease building projects depending upon each other. Right
now, the last of these modules is a "war" artifact which, after
building all modules, I would like to deploy to some server (using
exec:exec and the "asadmin" utility). 

Declaring this inside a "war" artifact, execution phase "deploy", works
fine. Using a "pom" artifact however, it seems to run "exec:exec" not
along with deploying the "pom" (i.e. after rebuilding all) but in the
"deploy" phase for each module (at least that's what the error messages
make me believe). Am I right on that? If so, how to achieve the effect
I would like to have, using such a configuration?

Thanks in advance and bye,
Kristian

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: exec:exec with "pom" artifact?

[Kristian Rink <ka...@zimmer428.net>]

Am Thu, 19 Jun 2008 11:53:53 +0200
schrieb Dirk Olmes <di...@xanthippe.ping.de>:

> I'm quite sure that this is not what you want. If you want to perform 
> some task at the end of the build, add a module (which can have a POM
> of packaging pom as well) and do the necessary steps there. Declare
> the proper dependencies to make sure it really runs as last build
> step.

Okay, I'll go for this approach then and see how far it does get me.
By now, thanks a bunch for your help on that. :)

Cheers,
Kristian

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: exec:exec with "pom" artifact?

[Dirk Olmes <di...@xanthippe.ping.de>]

> Declaring this inside a "war" artifact, execution phase "deploy", works
> fine. Using a "pom" artifact however, it seems to run "exec:exec" not
> along with deploying the "pom" (i.e. after rebuilding all) but in the
> "deploy" phase for each module (at least that's what the error messages
> make me believe). Am I right on that? If so, how to achieve the effect
> I would like to have, using such a configuration?

This sounds like you're declaring the exec plugin in some kind of parent 
pom which inherits that plugin invocation to all child modules then.

I'm quite sure that this is not what you want. If you want to perform 
some task at the end of the build, add a module (which can have a POM of 
packaging pom as well) and do the necessary steps there. Declare the 
proper dependencies to make sure it really runs as last build step.

-dirk

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org