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=32551>. 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=32551 Summary: Add path support to <import> task Product: Ant Version: 1.6.2 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I'd like to request the addition of filelist support to <import>. I am trying to build a "backstop" system where users may or may not pull the complete "build library" from the CM repository. If the library isn't in the developer's personal workarea (read: home directory) then all import operations go against a list of alternate locations (KGB, integration area, team shared area, etc.) Currently I'm using <available> to check a list of possible places, but this has the drawback of requiring lots of code to support what amounts to a filelist. I'd like to see <import> operate like many other tasks and accept a fileset or filelist as a contained element. Then I could write: <import> <filelist>...</filelist> </import> and have <import> bring in the first file located. (Fileset support would be "nice to have" but not quite so useful in my case because it's not ordered and I cannot guarantee that only one occurrence of the file exists.) Ideally would be a top-level <vpath> element, but that seems much harder. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
