Hi Andy and all, > I think we should look into the > Ant task (even if it's optional) that combines multiple Jar > files into a single jar. We could then build separate jars for > each module and the default target would combine them into the > single jar file we have today.
Only one caveat here: what we do now is copy all files we want in a jar to a particular directory, then compile them to a different directory, then jar up the result. The nice thing about this approach is that if you get a jar at all it's guaranteed to be self-sufficient (provided the right API jar is present of course). Would the idea here be to keep the modules independent--in which case every component jarfile will have the impl package, for instance) or, if they're not to be independent, then how is dependency-tracking handled? Would we even distribute them all, or just delete the little ones by default and keep only the standard one? Definitely an idea to look into though; I'm just not sure it'll be entirely straightforward. Cheers, Neil Neil Graham XML Parser Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
