Apparently, I've now got to include a log4j.properties file in the directory
containing my project's Ant build file, otherwise I just get a message
telling me Log4J hasn't been properly configured instead of being told what
files are being generated...
Couldn't it pick up a default configuration from a resource in the jar?
Also, I was wondering whether maybe those particular messages should have
been left as System.out.println's, since presumably you'd still want them
displayed even with logging turned completely off? And I don't think the
"Create ejb-jar.xml" etc. messages really need to include the category and
line number information.
I also just updated the xdoclet.jar which that project was using, and it
started dropping out with a NoClassDefFoundError for
org.apache.tools.ant.BuildException when I tried to build it, until I added
"${java.class.path}" to the <ejbdoclet> task's classpath attribute (I guess
adding ant.jar would have worked just as well). Why should it need the ant
classes in there, as opposed to the taskdef's classpath? (I tried adding
them there first, but it didn't help)
By the way, the document task in core/script/build.xml seems to have the
same problem.
Andrew.
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/xdoclet-devel
