custom lifecycle without inheritance

[Ben Tatham <be...@nanometrics.ca>]

Hello,
I am trying to invoke a single goal before another (ant-based) Mojo
executes.

Due to http://jira.codehaus.org/browse/MNG-5405 I cannot just do
<exeecution><goal>foo:bar</goal></execution> in the mojo.xml for the plugin.

So instead, I've defined a lifecycle.xml, with only one goal in it.

This works fine as a workaround for now, except that the forked lifecycle
inherits the goals from the lifecycle of the project that is running the
mojo in the first place.  In some of our projects, we have a lot of custom
mojos running, even in the initialize phase.

So...is there a way to:
a) define a new phase name (I don't think so)
or
b) make it so that the lifecycle.xml only runs what is defined there and
does not inherit the project's lifecycle?

-- 
Ben Tatham
Software Developer
Nanometrics Inc.
+1 613-592-6776 x254
http://www.nanometrics.ca

Fwd: custom lifecycle without inheritance

[Ben Tatham <be...@nanometrics.ca>]

Hello,
I am trying to invoke a single goal before another (ant-based) Mojo
executes.

Due to http://jira.codehaus.org/browse/MNG-5405 I cannot just do
<exeecution><goal>foo:bar</goal></execution> in the mojo.xml for the plugin.

So instead, I've defined a lifecycle.xml, with only one goal in it.

This works fine as a workaround for now, except that the forked lifecycle
inherits the goals from the lifecycle of the project that is running the
mojo in the first place.  In some of our projects, we have a lot of custom
mojos running, even in the initialize phase.

So...is there a way to:
a) define a new phase name (I don't think so)
or
b) make it so that the lifecycle.xml only runs what is defined there and
does not inherit the project's lifecycle?

-- 
Ben Tatham
Software Developer
Nanometrics Inc.
+1 613-592-6776 x254
http://www.nanometrics.ca





-- 
Ben Tatham
Software Developer
Nanometrics Inc.
+1 613-592-6776 x254
http://www.nanometrics.ca