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 20635] New: - Could the copy task use path-like structures ?
Date Tue, 10 Jun 2003 08:35:24 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20635>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20635

Could the copy task use path-like structures ?

           Summary: Could the copy task use path-like structures ?
           Product: Ant
           Version: 1.5.3
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Core tasks
        AssignedTo: dev@ant.apache.org
        ReportedBy: nicolas.lehuen@thecrmcompany.com


Hi,

In my Ant file I define a few <path>s with ids that I reuse in all my tasks
(compile, unit tests, javadoc, etc.). In the "dist" target, which build a
distribution zip, I'd like to copy all jars referenced in the <path>s I defined
in a "lib" directory (the jars are initially stored in a "3rdparty" directory
holding the full distribution directory of each 3rd party project I use).

The problem is that the copy task can handle filesets and dirsets, but won't
handle path-like structures, so I have to duplicate all my path entries with
fileset entries.

Another solution would have been to be able to define global filesets with ids,
and reuse it in javac as well as in copy, but it seems that filesets cannot be
defined on the project level, unlike path-like structures. I once defined
patternsets with an id in a "init" target, but patternset have the disadvantage
of not being standalone, i.e. they must be included later on in a fileset that
gives them a root directory...

So could it be possible to add support for path-like structures as a source
specification in the copy task ?

And I don't know if this is planned for version 2.0, but would it be possible to
reduce the number of kinds of file/path/directory specification types ? The
"Concept and Types" document presents 7 different ways of handling files and
paths... And core or optional tasks don't always use the same types, so it's
very difficult to globally define one set of files and reuse it in many tasks.

Best Regards,
Nicolas Lehuen

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


Mime
View raw message