> > a class examiner that compares the properties of 2 classes to make sure > > they are the same. > > jenesis (http://www.inxar.org/jenesis/) would probably come in handy for > that. I suppose our XJavadoc engine might well also help > (o:
Of course! > > These would be somewhat more complex than running diff on text files, > > however I think it might be worthwhile to avoid sensitivity to > formatting > > changes. > > yeah - the main problem being that at some stage someone would need to sit > down and do a sizable chunk of up-front work. how about, > use jenesis to parse the cvs version of an generated file, then parse the > new generated file, and do a content comparison - that > would avoid the whitespace problem, and avoid someone having to do the > upfront programming, and the maintainence. on the bad side, > I imagine it'd be dog slow as a test. so have that for source code, your > xml comparator for xml output, and we should have a pretty > solid "change observer" xjavadoc will be able to do the content comparison. You can easily compare class/method signatures, but what about actual code? How do you check if the body of the generated DO.equals() has the code you're expecting?! Ara. _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
