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/08/19 11:56:18 UTC
DO NOT REPLY [Bug 22540] New: -
FileSet throws BuildException where directory doesn't exist
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=22540>.
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=22540
FileSet throws BuildException where directory doesn't exist
Summary: FileSet throws BuildException where directory doesn't
exist
Product: Ant
Version: 1.5.3
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Core tasks
AssignedTo: dev@ant.apache.org
ReportedBy: tomasz@rtsoftware.com
FileSets do throw BuildException (for instance as a zipfileset used within a
Jar Task) if a directory doesn't exist.
I wanted to make a general ant build script, that could be used for all my
projects. The problem was that several directories are optional, some projects
do have them, some don't.
This caused quite of a headache, since I couldn't just make a general jar
structure, where optional directories could be left out.
I had to either make a different jar directory structure depending on the
project, or create empty directories, so that FileSet wouldn't nag.
The questions is - could it be controlled by a new attribute of the FileSet
type? Should I do it myself?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org