Hi Eric,
Good point. As the war plugin supports the war:webapp goal, Cactus ought
to support it too. Here's what I propose:
- the Cactus plugin does *not* perform the initial war-ing. This is left
to the user.
- the Cactus plugin offers a maven.cactus.prewar.dir property that
points by default to ${maven.war.build.dir}
- the Cactus plugin checks if "${pom.dir}.war" exists in
maven.cactus.prewar.dir, if not, it tries for a "${pom.dir}" directory
(expanded webapp).
Thus, as a user you would have to run first one of the war goal and the
only Cactus. For example:
maven war cactus:test-tomcat-4x
I believe this is provides better SOC.
Of course, if your container is Tomcat 4.x for example, you could have a
goal in your project maven.xml, like:
<goal name="cactus-test">
<attainGoal name="war:webapp"/>
<attainGoal name="cactus:test-tomcat-4x"/>
</goal>
What do you think?
Thanks
-Vincent
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:EPugh@;upstate.com]
> Sent: 08 November 2002 01:25
> To: [EMAIL PROTECTED]
> Subject: One more Issue with Cactus Plugin
>
> I need to set a series of properties. I currently do a war:webapp,
and
> then
> as a post goal, replace tokens for environment specific things.
However,
> I
> notice that the cactus plugin only calls war:war, which doesn't give
me a
> chance to edit things..
>
> I tried adding a pregoal on cactus:war to replace the files in the war
> with
> my edited files from my war:webapp, but it seems once the files are
in,
> they
> stay in, and can not be replaced. Any ideas?
>
> Would it be possible to point cactus to build a war from an exploded
war
> directory?
>
> Eric Pugh
--
To unsubscribe, e-mail: <mailto:turbine-maven-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:turbine-maven-dev-help@;jakarta.apache.org>
