Two issues: Firstly, is it possible to have an old style distribution build target? Currently just to build some ejb's I need:
xdoclet.jar xdoclet-xdoclet-module.jar xdoclet-appserver-module.jar commons-logging.jar xjavadoc.jar Compared to just an xdoclet.jar previously. Now, I appreciate that this new design is better and more modular etc etc, but I suspect I'm missing something as I detect a small bit of overengineering... Eg, when would someone want xdoclet.jar without xdoclet-xdoclet-module.jar? I also miss the ability of just adding a line to my build file to emit dd's for new appservers, now I have to find the appropriate module jar and put that in my already-very-full build classpath. Secondly, it is possible to specify nested classpath ref elements in defining tasks? (ok, I guess this is an ant question...) Eg, instead of specifying classpathref="someref", I'd like to use nested elements since I have more than one classpath ref. This didn't seem to work when I tried it. ------------------------------------------------------- Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
