db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@debrunners.com>
Subject Re: Sharing code
Date Mon, 05 Sep 2005 04:11:26 GMT
Jeremy Boynes wrote:

> David W. Van Couvering wrote:
>> The common classes will be placed into both derby.jar and
>> derbyclient.jar.  When you have a classpath with a network client at
>> one revision and the embedded driver at another revision, the jar with
>> the highest revision should always go first, e.g
>> "/home/derby/10.2/derbyclient.jar:/home/derby/10.1/derby.jar".  This
>> ensures that the newer code that depends on new interfaces (e.g. a new
>> method for a class) will be able to function properly.
> Others have pointed out the problems here with classpath ordering.
> The root of this is that the same classes are being included in multiple
> jars leading to potential duplication. This can be avoided by placing
> them in a separate jar so that each is only present once e.g.

Not true, the problem exists if the classes are in a single jar or
multiple jars.


View raw message