ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 22269] - files pattern in <import/>
Date Sun, 13 Nov 2005 22:29:22 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=22269>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=22269





------- Additional Comments From mikecepek@yahoo.com  2005-11-13 23:29 -------
Additional desired requirement:  the <import> task should accomodate redundant
imports, either by importing each build file only once per Ant invocation OR by
simply behaving well (i.e. not generating errors or warnings) when importing a
given build file more than once per Ant invocation.

This will eliminate messy Ant "exclude" logic in many cases.  For example,
consider a subpackage which relies on the parent package to import all build
files for that package.  If the Ant invocation started with the subpackage build
file, then that build file will already have been read in when the parent
package attempts to import all the subpackage build scripts (using a <fileset>).

It's quite a pain to code each subpackage to exclude itself from the parent
package's bulk import of the subpackage build scripts.  I already struggle with
this in my hierarchical build scripts which current <import> each subpackage
build file separately.  This "smart import" feature will make a big difference
in usability.

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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message