> Not for me. The latest template has
>
> assertEquals(
> tokenizeAndTrim("<XDtMethod:methodTagValue
> tagName="param"/>"), paramTags[t].value() );
>
> in the parameter checking at the end; I had to
> change that to
>
> assertEquals(
> tokenizeAndTrim("<XDtMethod:methodTagValue
> tagName="param"/>"),
> tokenizeAndTrim(paramTags[t].value()) );
>
> to avoid any failures. This was with a copy updated
> this morning; I did a
> build clean/total-clean on all three modules, then
> tried a build in
> xjavadoc. 30 failures, including the two ant
> classes Aslak changed over the
> weekend... (which is why I suspected pretty)
Well, I also updated this morning ( shall I do this
again? ) and there is:
assertEquals( tokenizeAndTrim("c Describe what the
parameter does"), paramTags[t].value() );
Basically I just do not understand, what's point in
comparing something parsed by xjavadoc with something
parsed by even same xjavadoc from thge very same
source.
regards,
=====
Konstantin Priblouda ( ko5tik ) Freelance Software developer
< http://www.pribluda.de > < play java games -> http://www.yook.de >
< render charts online -> http://www.pribluda.de/povray/ >
__________________________________________________
Do You Yahoo!?
Yahoo! Games - play chess, backgammon, pool and more
http://games.yahoo.com/
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
