Doing a clean build of the current CVS xjavadoc, I get 28 junit failures, which are all of the form
expected:<fileName Describe what the parameter does> but was:<fileName Describe what the parameter does> i.e. the no. of spaces between the parameter name and description differs. At first, I assumed this was due to pretty reformatting the javadocs so the test strings didn't match, but looking at the generated code for e.g. XTag__GENERATED__Test.java I see that the assert does include the correct number of spaces. The problem is that it does a tokenizeAndTrim() on the string, but not on the value it's comparing it to. Adding this to xjavadoctest.j, I get no failures again (I'll commit it tonight). I thought the general rule was to avoid checking in stuff that fails the unit tests? Okay, so this particular case was relatively trivial, but if anything that just means there's even less excuse for it not being fixed first... Andrew. _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
