It seems that tasks that use mappers usually apply the mapper to a resource name; some tasks, like pathconvert, however, apply the mapper to the string representation of a resource (e.g. full path for a file resource). Do we consider pathconvert's behavior anomalous enough to call it a bug? Or rather, would we consider it so if we weren't afraid of breaking builds? I am thinking our basic approach should be to document that name-only is the usual usage, then document task-level exceptions to this "rule" as we encounter them. Opinions?
-Matt --- On Thu, 10/15/09, bugzi...@apache.org <bugzi...@apache.org> wrote: > From: bugzi...@apache.org <bugzi...@apache.org> > Subject: DO NOT REPLY [Bug 48001] Document differences between tasks' usage > of mappers in some fashion. > To: notificati...@ant.apache.org > Date: Thursday, October 15, 2009, 2:57 PM > https://issues.apache.org/bugzilla/show_bug.cgi?id=48001 > > Matt Benson <gudnabr...@yahoo.com> > changed: > > What > |Removed > |Added > ---------------------------------------------------------------------------- > Component|Core > tasks > |Documentation > Summary|Touch > task with fileset and |Document differences > > |a mapper does not create > |between tasks' usage of > > |new files. > |mappers in some > fashion. > > -- > Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are the assignee for the bug. > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
