You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2003/07/21 16:56:14 UTC
DO NOT REPLY [Bug 21770] New: -
ClassFileset should resolve vs. a classpath
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=21770>.
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=21770
ClassFileset should resolve vs. a classpath
Summary: ClassFileset should resolve vs. a classpath
Product: Ant
Version: 1.5.3
Platform: Sun
OS/Version: Solaris
Status: NEW
Severity: Enhancement
Priority: Other
Component: Optional Tasks
AssignedTo: dev@ant.apache.org
ReportedBy: hanafey@dna.es.dupont.com
Why does ClassFileset not take a "classpath" from which to find dependencies?
This would allow the destination jar to include parts of libraries contained
in jar files.
The genjar optional task does this, but currently it does not do dependency
checking. With a properly generated ClassFileset, the normal dependency checking
of the jar task would be available.
It also seems much cleaner to not have a special genjar task to create a
"linked" jar file, given that this seems naturally to just be a special fileset.
Maybe the only stretch is a fileset could then also represent a set of files
contained in a jar or zip file.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org