A wise old hermit known only as Marcus Brito <[EMAIL PROTECTED]> once said:
> Could someone explain me if there is a way to debug xDoclet code in an > integrated debugger like those of commercial IDE's? (I'm using IDEA). I > tried putting ant + xdoclet + xjavadoc in the ide path and definid the > main ant class as the main application class.=20 > > However, as the xDoclet task is forked, it doesn't seem the IDE debugger > catches the breakpoints. Has someone sucessfully debugger (with > breakpoints and all) xDoclet in such IDE? I think I have a similar problem - I'm trying to run xjavadoc & xdoclet's unit tests through jprobe's code coverage tool (I've got about a week left to run on an evaluation copy of it) to see how complete the tests are. However, you have to launch the app through their GUI so that it can include the necessary parameters to the JVM (it uses JVMPI). I think I've got it running the build script okay, by doing much the same as you (setting the classpath to include the stuff build.bat puts in there and using the Ant main class as the class to run), but I suspect the task forking will interfere with gathering the profiling info also (unless that inherits the JVMPI settings and opens another socket connection to their GUI as it starts running). Unfortunately, I haven't got far enough with it to tell - it keeps freezing part way through the [pretty] stuff, but I believe that's a separate issue. By the way, does anyone know of a free and/or open source code coverage tool I can download for when jprobe expires on me? I tried searching for various combinations of "jvmpi", "java", "code", "coverage" on google last week, but only found profilers (which were next on my list, but I wanted to check the tests' coverage first). Andrew. _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
