> On Mon, 27 Dec 2004 15:48:00 -0800, Martin Cooper <[EMAIL PROTECTED]> wrote: > > > Not me. Doing this will lead to people having multiple copies of > > various component jars lying around on their disks, and will > > unnecessarily increase the amount of stuff that people need to > > download. Definitely true, but it's petty change however. The people who have this problem (clutter) are likely to have this problem already. > > For example, suppose I use Digester and Betwixt. I download them both, > > and now I have two copies of Digester, BeanUtils and Logging. But if I > > actually wanted to use BeanUtils itself, I'd need to download it > > again, because I only have the jar file, and not the JavaDocs or other > > contents of the distro. This partly leads me on to a different issue that I think we need to improve; Javadoc management; but I don't think this is a very big deal. > > It's also not clear to me that every component is going to comprise a > > single jar for the purposes of inclusion into another distro. In such > > cases, there would need to be some well-defined structure for the > > additional files. This is already solved in the project.xml. > > One more: How do you define dependencies? What happens in cases such > > as Resources, where there are multiple optional implementations? Do we > > include all of them, or just some of them, and how would we decide? > project.xml. You add a property to each dependency that you wish to include in the distribution. For an example like Resources, I've no idea. I imagine it would depend on the particular situation. Hen
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
