[Db-derby Wiki] Trivial Update of "SharedComponentVersioningGuidelines" by DavidVanCouvering

[Apache Wiki <wi...@apache.org>]

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

------------------------------------------------------------------------------
  No visible impact  implies the following checkin requirements for any
  common code.
  
+    * derbyclient.jar, derby.jar, and derbytools.jar  of the same major version can continue to be mixed within the same JVM classpath without
-    * derbyclient.jar, derby.jar, and derbytools.jar  of the same major
- version can continue to be mixed within the same JVM classpath without
- any difference  in behavior from loading these  jars in separate
+ any difference in behavior from loading these jars in separate classloaders.
- classloaders.
     * Jar file growth is commensurate with functionality improvement.
-    * Replacing  any jar  with a jar of the same major version  will not require any user classpath changes.
+    * Replacing any jar with a jar of the same major version will not 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.