This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
• Reports Illegal API use Binary incompatibility relative to a baseline Incorrect bundle version numbers Missing or malformed @since tags Leakage of non-APIs types inside APIs Invalid references inside system libraries
• Tightly integrated toolset in the Eclipse SDK Currently limited to Plug-in projects/OSGi bundles Runs as a builder (auto-build, incremental and full builds) Immediate feedback as you develop and use APIs
E.g. @noimplement, @noextend, @noreference, @noinstantiate
• Benefits Contracts live with the code for producers and consumers Content assist helps developers Available for projects that are not using 1.5 annotations Restrictions appear in published Javadoc APIs in a standard
• Evolving APIs such that they are backwards compatible with existing binaries http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs It is easy to get it wrong Now the tooling takes care of this
• The user simply specifies an API baseline Generally this means pointing to the previous release
• This can be generated once an API usage report is available
• A migration report is generated from: an API use report A newer release of the API being used
• It detects all possible migration issues that could occur between the version from which the API usage report has been generated and the current version Note: problems with constants will not be detected
source code in it are made available under the EPL, v1.0.• Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in
the United States, other countries, or both.• Eclipse and the Eclipse logo are trademarks of Eclipse Foundation, Inc.• IBM and the IBM logo are trademarks or registered trademarks of IBM Corporation,
in the United States, other countries or both.• Other company, product, or service names may be trademarks or service marks of
others.• THE INFORMATION DISCUSSED IN THIS PRESENTATION IS PROVIDED FOR
INFORMATIONAL PURPOSES ONLY. WHILE EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION, IT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, AND IBM SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE USE OF, OR OTHERWISE RELATED TO, SUCH INFORMATION. ANY INFORMATION CONCERNING IBM'S PRODUCT PLANS OR STRATEGY IS SUBJECT TO CHANGE BY IBM WITHOUT NOTICE