I agree with you that support is as important as technology. But in this case your problem could simply be resolved by creating a directory lib/xdoclet containing only the xdoclet jars. In the ant project you could simply include "lib/xdoclet/*". So instead of saying "grab all the xdoclet jars" you'll say "grab the whole xdoclet dir". Moreover if I need only support for Weblogic and JBoss (for example) I have not to copy ALL the jars. And if later I need support for something else I simply drop in another jar in lib/xdoclet.
Marco > > Subject: RE: [Xdoclet-user] Packaging XDoclet in One Jar? > Date: Tue, 11 Feb 2003 15:52:18 -0500 > From: "Adam Houghton" <[EMAIL PROTECTED]> > Reply-To: [EMAIL PROTECTED] > To: <[EMAIL PROTECTED]> > > I've managed to get the jar number down to ten (six core/EJB/web + four app >server-specific). That's definitely a more manageable number than thirty. > > Still, in my situation, it would be easier to deal with one jar than ten. I'm going >to put XDoclet in a company-wide repository of jars. When developers want to use >XDoclet on a project, it would be simpler to tell them "grab xdoclet.jar and add this >ant task" instead of "grab these ten jars in order to do these things". Inevitably >someone will only grab xdoclet-1.2b2.jar and wonder why XDoclet doesn't work. > > So really, it's more of a support/learning curve issue than a technology issue. Not >a huge deal, but I thought I'd check and see. Since there's no easy way to make one >jar, I'll just add all ten and document the process. Perhaps having an option to >build as one jar could be something to look at for version 2. > > Thanks, > Adam > -- Unite for Java! - http://www.javalobby.org ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
