Bug 57924 - AbstractFileSet expects dir even if erroronmissingdir="false"
Summary: AbstractFileSet expects dir even if erroronmissingdir="false"
Status: NEW
Alias: None
Product: Ant
Classification: Unclassified
Component: Core tasks (show other bugs)
Version: 1.9.4
Hardware: PC All
: P2 normal (vote)
Target Milestone: ---
Assignee: Ant Notifications List
Depends on:
Reported: 2015-05-12 14:52 UTC by franz.hagel
Modified: 2015-05-14 05:11 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description franz.hagel 2015-05-12 14:52:58 UTC
AbstractFileSet.getDirectoryScanner(Project p) throws BuildException("No directory specified for XXXX") even if erroronmissingdir="false" was specified on the fileset. What is the difference between specified dir does not exist and dir was not specified?
Comment 1 Stefan Bodewig 2015-05-14 05:11:00 UTC
The erroronmissingdir="false" setting is used in a situation where you try to create a generic build that may or may not want to include some optional resources - and happily goes on when those optional resources are not there.

I'm not sure what a <fileset> without a base directory would be used for, what is your use-case?  The only thing I can imagine is something like <zipfileset> which can read from an archive rather than a directory, but this one simply overrides getDirectoryScanner (in ArchiveFileSet).