I solved my problem by witting my own plugin that I can add to the maven
command line in exactly the places I need it to run. It was much easier
than I thought it would be.
On Mon, Oct 13, 2008 at 7:31 PM, Brett Porter <[EMAIL PROTECTED]>wrote:
> Using a well known project property is probably t
Using a well known project property is probably the best alternative.
This has the advantage of also being able to be used in the project
itself to temporarily disable the functions, but has the drawback that
if anything persists the project the property will be visible.
However, antrun doesn't ha
I was going to attach a fourth run to pre-site that would set the property
to block the others.
On Sun, Oct 12, 2008 at 7:43 PM, Brett Porter <[EMAIL PROTECTED]>wrote:
> I don't quite understand your use case. Wouldn't it always run in
> validate and block the others?
>
> 2008/10/12 Jon Strayer <
I don't quite understand your use case. Wouldn't it always run in
validate and block the others?
2008/10/12 Jon Strayer <[EMAIL PROTECTED]>:
> I have some executions attached to three phases (validate, process-resources
> & process-classes) that it would like to execute only once per build.
> What
I have some executions attached to three phases (validate, process-resources
& process-classes) that it would like to execute only once per build.
What's the best way to achieve that?
I tried using the ant-run plugin to set a property but that doesn't seem to
be working (I haven't figured out why
