DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4065>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4065 Regexp mapper and classpath ------- Additional Comments From [EMAIL PROTECTED] 2001-11-13 07:52 ------- It is ? Then that's a documentation bug (that's the kind of bug I *love*). However will it work better than classpathref here ? A for bug#3934, if there are no references to another regexp parser in ant internal classes, I don't see why it should apply. As far as I see the problem is not clashes between my jar specification and some internal ant one, but that somehow ant forgets to seeache the specified classpathref for a valid RegexpMatcher -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
