[Bug 57924] New: AbstractFileSet expects dir even if erroronmissingdir="false"

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=57924

            Bug ID: 57924
           Summary: AbstractFileSet expects dir even if
                    erroronmissingdir="false"
           Product: Ant
           Version: 1.9.4
          Hardware: PC
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Core tasks
          Assignee: notifications@ant.apache.org
          Reporter: franz.hagel@nuernberger.de

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?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 57924] AbstractFileSet expects dir even if erroronmissingdir="false"

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=57924

Stefan Bodewig <bo...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 OS|                            |All

--- Comment #1 from Stefan Bodewig <bo...@apache.org> ---
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).

-- 
You are receiving this mail because:
You are the assignee for the bug.