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=8794>. 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=8794 Junit XMLresultformatter doesnt work if xml stuff isnt on the junit path [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE Summary|Junit XMLresultformatter |Junit XMLresultformatter |doesnt work if xml stuff |doesnt work if xml stuff |isnt on the junit path |isnt on the junit path ------- Additional Comments From [EMAIL PROTECTED] 2002-06-06 06:18 ------- I am marking this as a duplicate of 6019, as it probably really is manifest related. to wit: 1. Ant's manifest used to auto-pull crimson into the classpath 2. when we moved to xerces, crimson went away 3. all those tasks that depended on an xml parser (the xmlresultformatter), broke. I have done the update to the manifest to refer to xerces, not crimson, but the fundamental problem of bug 6019 remains, that we are secretly sneaking an XML parser into the classpath of <junit>. we need that parser for the result processing, but it shouldnt be visible to the unit tests themselves. *** This bug has been marked as a duplicate of 6019 *** -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
