Exactly! I was going to use the MANIFEST Class-Path: attribute as an example in my last message, but I wasn't sure if it was evaluated for any jar other than the original target jar.
On 9/28/05, Craig McClanahan <[EMAIL PROTECTED]> wrote: > Some sort of dependency declaration is going to be necessary for solving > this problem completely. There's precedent in the way that a JAR file can > declare dependencies on other JARs in it's MANIFEST.MF file ... something > like that should be explored here as well.
