ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 46526] New: Document behaviour of properties set in target called by antcall
Date Wed, 14 Jan 2009 10:03:17 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=46526

           Summary: Document behaviour of properties set in target called by
                    antcall
           Product: Ant
           Version: 1.7.1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Documentation
        AssignedTo: notifications@ant.apache.org
        ReportedBy: davidcorley@gmail.com


Having inherited a legacy build system, I came across strange behavior with an
antcall task. I found that properties set in the target called by the antcall
task were not available at later points in the build. I couldn't understand
this as the documentation states that properties are immutable.
It was only after coming across the antcall ant-contrib task that I understood
the antcall task behavior when it comes to properties set in the called target.

http://ant-contrib.sourceforge.net/tasks/tasks/antcallback_task.html

The current documentation for <antcall> in the Ant manual makes no reference to
the fact that:

a) A new Ant project is created
b) Any properties set in the target called by <antcall> are cleared after the
target has run.

Can someone please update the <antcall> manual page to reflect this
information?


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Mime
View raw message