Great! Just counter-intuitive... I think it's just me who's having a hard time grasping the mappers. Part of there complexities is compounded by the fact that most of the time they work on pathnames, without _understanding_ them in the sense that a regex matcher will consider / and \ differently, yielding many support questions. Regex for path should be normalized somehow prior to attempting the match. --DD
-----Original Message----- From: Stefan Bodewig [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 12, 2002 10:15 AM To: [EMAIL PROTECTED] Subject: Re: uptodate question On Thu, 12 Dec 2002, Dominique Devienne <[EMAIL PROTECTED]> wrote: > The mapper is fed a relative path to the fileset's > 'dir' (which is indeed ${basedir} in this case ;-), and turns it > into an absolute one? This would fail with code like new File(dir, > mapper.map(relativePath))... So the result of the mapper is first > checked to see if it's absolute, and if not prepended with 'dir'??? Well, SourceFileScanner does a FileUtils.resolveFile() on whatever mapper returns - this is guaranteed to return an absolute path and deas with absolute paths as input quite well. Stefan -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
