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 Tue, 18 Oct 2005 01:45:10 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

------------------------------------------------------------------------------
  
  }}}
  
- Note that the constant {{{CommonInfo.WHIZBANG_FEATURE}}} is compiled down to a constant
integer, so there will not be runtime errors if the older version of the component has been
loaded.
+ Note that the constant {{{CommonInfo.WHIZBANG_FEATURE}}} is compiled down to a constant
integer, so there will not be runtime errors if the older version of the component has been
loaded.S
- 
- '''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 ==
  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.

Mime
View raw message