db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "SharedComponentVersioningGuidelines" by DavidVanCouvering
Date Thu, 20 Oct 2005 22:04:39 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by DavidVanCouvering:
http://wiki.apache.org/db-derby/SharedComponentVersioningGuidelines

------------------------------------------------------------------------------
  any difference  in behavior from loading these  jars in separate
  classloaders.
     * Jar file growth is commensurate with functionality improvement.
-    * Replacing  any jar  with a jar of the same major version  will not
+    * Replacing  any jar  with a jar of the same major version  will not require any user
classpath changes.
- require any user classpath changes.
  
  The only exception is if for some reason (and this is to be avoided) a change is made between
major revisions that is not compatible, then if the user is running in a mixed version environment
in the same VM, he or she should attempt to ensure that the jar files from the newer version
are loaded first.  If for some reason this is not possible, the user will need to separate
the two versions by using separate classloaders within the same VM.
  

Mime
View raw message