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 have access to the project properties itself so that logic would need to be in plugins of their own. - Brett 2008/10/14 Jon Strayer <[EMAIL PROTECTED]>: > 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 <[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'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 yet). >> > >> > -- >> > Esse Quam Videre >> > To Be, rather than to Seem >> > >> >> >> >> -- >> Brett Porter >> Blog: http://blogs.exist.com/bporter/ >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > -- > Esse Quam Videre > To Be, rather than to Seem > -- Brett Porter Blog: http://blogs.exist.com/bporter/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
