Stefan Bodewig wrote:
On Mon, 06 Dec 2004, Peter Reilly <[EMAIL PROTECTED]> wrote:
This is not the case for the "glob" mapper and this has caused some
pain and some scripts to fail when moved from unix to windows and
visa-versa.
The same is true for the regexp mapper. Only things are a bit more complicated here, since \ also is a special character for the regexp engine.
Is true.
One can of course use ${file.separator}, but this does make the
scripts look ugly and one is not inclined to do this.
But likely is the only clean solution.
And does not work for the regex case :-(
One could add an attribute to globmapper to tell it to do the
interpertation ("handledirchars" ?), but it may be nicer just to
always interpret the / and \ in the same as the "includes", and
"include" attributes and elements in fileset et. al.
I'd prefer an explicit attribute and use the same attribute for the
regexp mapper as well.
I am neutral on this, will wait for consenus... also is the attribute (handledirchars) name ok??
Peter
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
