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

------------------------------------------------------------------------------
  
  The guidelines for shared components in Derby are based on the [http://jakarta.apache.org/commons/releases/versioning.html Jakarta Runtime Versioning Guidelines].  There are some areas that these guidelines do not cover, however, which we will address here:
  
+ [[TableOfContents]]
-    * Mixed Version support
- 
-    * Version publishing and detection
- 
-    * Guidelines for forward-compatibility
- 
-    * Deprecation guidelines and mechanisms
- 
-    * Packaging of common components
  
  == Mixed Version Support ==
  
@@ -81, +73 @@

  
  '''NOTE:''' I still need to investigate to see if you can have a method call to a non-existent method in your code as long as the code is never executed.
  
- === Deprecation Guidelines ===
+ == Deprecation Guidelines ==
  A method or an interface may be deprecated.  This is done using the @deprecated tag in the method or interface Javadoc.  A method or interface must be available for 2 major releases after it is deprecated.  For example, if it is deprecated in version 8.2, it can be removed in version 10.0 or greater.  An exception to this rule may occur if it becomes clear that there is still heavy use of this interface.
  
- === Distribution of Shared Components ===
+ == Distribution of Shared Components ==
  
  To help make explicit the various shared components within Derby and what is contained in them, our internal build will create a seprate JAR file for each shared component.