Btw, we could make it easier by simply turning DocletTask$Main traces on with a simple verbose="true" param of ejb/etcdoclet. Anyone volunteer to implement it (needs programmatically turning on log4j category trace on for that stuff).
Ara. > -----Original Message----- > From: nobody [mailto:[EMAIL PROTECTED]] On Behalf Of > [EMAIL PROTECTED] > Sent: Friday, January 25, 2002 1:33 AM > To: [EMAIL PROTECTED] > Subject: [xdoclet - Help] RE: trying debug javadoc/xdoclet > > > Read and respond to this message at: > http://sourceforge.net/forum/message.php?msg_id=1469969 > By: stevensa > > Well, I don't know about debugging, but there's a fair amount of debug > trace > output in there (using log4j). You could try switching that on. > According > to a message Ara sent to xdoclet-user a couple of months ago, > > "As a general rule, whenever you get an un-normal error "Xdoclet failed > blabla", please turn log4j on and let us see what the stack trace shows. > To do so: > > - make a copy of core/config/log4j.properties, put it where your > build.xml is. > - Uncomment the last line of it. > - Rerun Ant, this time add this parameter to Ant launcher: > -Dlog4j.configuration=file:/full_path/log4j.properties > (Assuming you launch Ant by java org.apache.tools.ant.Main blabla like > Xdoclet's samples)" > > ______________________________________________________________________ > You are receiving this email because you elected to monitor this forum. > To stop monitoring this forum, login to SourceForge and visit: > http://sourceforge.net/forum/monitor.php?forum_id=99268 _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
