I got around this issue in the end by using Ant 1.6's new macrodef
feature, this allows you to easily create a macro instead of a
callable ant target.
See
http://ant.apache.org/manual/CoreTasks/macrodef.html
so I put the Macrodef's in the same build file and called them where necessary.
Pete
On 16/06/06, cristal <[EMAIL PROTECTED]> wrote:
The only work-around to this issue is to add a line of ant script in the
target before you invoke the <antcall>task, like this
<copy file="/my/plugin/path/mymojo.build.xml"
tofile="/my/plugin/path/build.xml" />
so that there is always a build.xml available in the directory by the time
<antcall> is executed. But you will always need to remember the
"mymojo.build.xml" is the real one for you to work with when you modify the
mojo plugin.
It's ugly but works for me.
--
View this message in context:
http://www.nabble.com/-m2--problem-w--antcall-in-ANT-based-mojo-t1307160.html#a4905731
Sent from the Maven - Users forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
