On 31/10/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> You actually just need the lifecycle.xml as described in the build
> lifecycle document, not the custom packaging. That lifecycle
> "overlay", inc onjunction with the original packaging and the
> lifecycle-"exploded" attribute on @execute should do the trick.
Thanks Brett, I did try this initially but m2 doesn't seem to like
invoking goals outside of the plugin in lifecycle.xml. For example, I
have @execute phase = "package" lifecycle = "exploded" on my mojo and
the following lifecycle.xml:
<lifecycles>
<lifecycle>
<id>exploded</id>
<phases>
<phase>
<id>package</id>
<executions>
<execution>
<goals>
<goal>org.apache.maven.plugins:maven-war-plugin:exploded</goal>
</goals>
</execution>
</executions>
</phase>
</phases>
</lifecycle>
</lifecycles>
I've also tried just <goal>war:exploded</goal> but in both situations it says:
[ERROR] BUILD ERROR
[INFO]
----------------------------------------------------------------------------
[INFO] Required goal
'org.apache.maven.plugins:maven-war-plugin:exploded' not found in
plugin 'tomcat'
Sorry for the hassle, but all other examples seem to invoke goals
within their plugin only.
Cheers,
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
