https://issues.apache.org/bugzilla/show_bug.cgi?id=46526
--- Comment #2 from David Corley <[email protected]> 2009-01-14 07:29:29 PST --- (In reply to comment #1) > ! /Users/mbenson/oss/asf/ant/docs/manual> grep -ci "new project" > CoreTasks/antcall.html > 10 > ! /Users/mbenson/oss/asf/ant/docs/manual> > > -------- > > I will concede that the manual could be more explicit: "The called target(s) > are run in a new project; be aware that this means properties, references, > etc. > set by called targets will not persist back to the calling project." > > Finally, you should be aware that for probably going on five years now macros, > rather than <antcall>ed targets, are the preferred way to perform > compartmentalized tasks within your build. I don't believe I've run into a > situation where a macro wouldn't suffice for what I was trying to accomplish. > I agree about macros and I use them wherever possible. In fact this was part of the reason I came across this issue. I was not used to using antcall (inherited old build code) and didn't understand its behavior. Anyway, thanks for the update. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
