Heya,
> You can check out the various macroforeach tasks
> around to get an idea of what you need to do.
This hint lead me to AntExtra, which provides a
task that accepts makro names.
Thanks,
Felix
-
To unsubscribe, e-mail:
You can invoke macros easily from Java or Groovy. Groovy is easier,
but if you want to write a task, it isn't too difficult. You can check
out the various macroforeach tasks around to get an idea of what you
need to do. Or just invoke it from groovy like:
ant."${x}"(...)
Pretty certain t
_
Get quick access to your favorite MSN content with Internet Explorer 8.
http://ie8.msn.com/microsoft/internet-explorer-8/en-us/ie8.aspx?ocid=B037MSN55C0701A
-
To
Well I assume it would be easy to write a contributed task
similar to the one that I describe above. The only thing I'd
need to know is how to execute a macro with a given name from
within a Task implementation...
> I understand what you mean now. You want all possible values
> to be taken car
I understand what you mean now. You want all possible values to be taken
care of. Not sure if I can think of anything off-hand that would do that.
On Tue, Mar 24, 2009 at 1:30 PM, Felix Dorner wrote:
> Hey David,
>
> Thanks for your suggestions.
>
> > Well the only reason I specified the method
Hey David,
Thanks for your suggestions.
> Well the only reason I specified the method below is that you
> asked what could be done with ant-core.
> However, if you're able to use ant-contrib, then you can
> simplify it a little more using the ant-contrib task.
Of course this is a possibility,
Well the only reason I specified the method below is that you asked what
could be done with ant-core.
I don't think you can do much more than what I've suggested.
However, if you're able to use ant-contrib, then you can simplify it a
little more using the ant-contrib task.
So:
This approach would make the macros obsolete. Instead I
would move the macro code into the targets you mention, and could do
This is actually how my build file currently looks like. But I
want to switch to macros as they are more lightweight and controllable.
Felix
> You'd probably be better
You'd probably be better have individual properties as flags for each macro.
So something like:
So you set individual properties depending on the value of ${x}. The
individual properties can then be used to determine whether particular
targets containing each macro are run.
