Content Comparison

...

The

Insert excerpt
ApplicationName ApplicationName nopanel true ApplicationName

 framework, like all software, will mature over time.  Changes will be made to improve efficiency, add features, and fix bugs.  To ensure that compontents built for

Insert excerpt
ApplicationName ApplicationName nopanel trueApplicationName

 and its sub-frameworks are compatible, developers must be aware when and where they establish dependencies from developed components.

Guidelines for Maintaining Compatibility

Insert excerpt
ApplicationName ApplicationName nopanel true

...

 Framework

For components written at the

Insert excerpt
ApplicationName ApplicationName nopanel true ApplicationName

 Framework level (see Developing at the Framework Level), adhere to the following specifications: 

...

Warning
Avoid developing dependencies on the implementations directly, as compatibility in future releases cannot be guaranteed.

Insert excerpt
ApplicationName ApplicationName nopanel true

...

 Catalog API

For components written for the

Insert excerpt
ApplicationName ApplicationName nopanel true ApplicationName

 Catalog (see Developing Catalog Components), only dependencies on the current major version of the Catalog API should be used.  .  Detailed documentation of the Catalog API can be found in the Catalog API Javadocs.

Insert excerpt
ApplicationName ApplicationName nopanel true

...

 Software Versioning

Insert excerpt
ApplicationName ApplicationName nopanel trueApplicationName

 follows the Semantic Versioning White Paper for bundle versioning (see Software Versioning).  

...