Then unjar all your dependent JARs somewhere, and make <classfileset> work for you, or file a bug report in BugZilla if you think you've found a bug.
--DD PS: Off topic, but is it OK to include part of projects classes in your own JARs, when these other projects are Open Source released under various licenses? Does the Apache or Jakarta license prevent that? -----Original Message----- From: Aaron Kelley [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 11, 2002 10:24 AM To: 'Ant Users List' Subject: RE: Efficient method to build JARs I don't need any tool to guess which classes I am loading dynamically. I want to define a fileset of these classes (so include all the classes in folderX as my root classes) and then have the tool load all of their dependencies (very similar to what ClassFileSet does, but I need it to actually work, and I need to do something about all my required classes in JAR files). We are using quite a few required libraries and our JAR file will be downloaded to clients, so size does matter. -----Original Message----- From: Dominique Devienne [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 11, 2002 9:15 AM To: 'Ant Users List' Subject: RE: Efficient method to build JARs I fail to see how any tool could *guess* which classes you'll dynamically load from your code, except if you have a very controlled way of specifying the list of such classes (their names I guess). Packaging more classes than needed is better than not finding them at runtime once deployed. Or I'm missing something altogether. --DD -----Original Message----- From: Aaron Kelley [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 11, 2002 10:10 AM To: [EMAIL PROTECTED] Subject: Efficient method to build JARs Is there an efficient way to build JARs (so it loads all the dependencies and not every class file)? I see that there is a ClassFileSet, but it cannot pull required classes from JAR files. Also, I could not really get it to work and there seems to be a lack of documentation for it. Secondly, I looked at GenJar, but this package requires you to actually list individual classes that form the root of your dependencies. My problem with this package is that I would have to list all of my classes since we are dynamically loading many of classes in out projects. This is not an option since I will be using it for automated building of large and changing projects. I would love to hear any other options I may have. Thanks, Aaron -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
