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] Trivial Update of "ModuleVersioningGuidelines" by DavidVanCouvering
Date Thu, 22 Sep 2005 05:06:01 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/ModuleVersioningGuidelines

------------------------------------------------------------------------------
  
  == Mixed Version Support ==
  
- As much as possible, two applications should be able to use different versions of Derby
code within the same Java VM without having to resort to creating specialized classloaders.
 This is enabled by supporting forward compatibility as described below.  
+ As much as possible, two applications should be able to use different versions of Derby
within the same Java VM without having to resort to creating specialized classloaders.  This
is enabled by supporting forward compatibility as described below.  
  
  == Version Publishing and Detection ==
  
@@ -28, +28 @@

  
  == Guidelines for Forward Compatibility ==
  
- It is important that shareable modules are as interoperable as possible across versions.
 This includes not just backward compatibility but also forward compatibility.  
- 
  Wherever possible, a consumer built against version X.Y of a module should work with version
X.Y' of a module where Y' < Y.  If the consumer uses new functionality added in version
X.Y of the module, it should degrade to X.Y' level functionality.  In the rare cases where
this is not achievable, the consumer should throw an exception explaining that it requires
version X.Y or greater of the module (rather than an obtuse Java exception like `NoSuchMethodException`).
 The consumer takes adavantage of the version detection mechanism described above to query
the version of the module and then take appropriate action.
  
  === Deprecation Guidelines ===

Mime
View raw message