Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Plugin Development Environment (PDE) » Unable to check API compatibility(use of new API not flagged)
Unable to check API compatibility [message #765496] Wed, 14 December 2011 07:40 Go to next message
bstephenson is currently offline bstephensonFriend
Messages: 1
Registered: December 2011
Junior Member
Trying to check API compatibility using the API tooling. Enabled own plugins for API builder and set a baseline from a previous release of Eclipse 3.2.2 ( 3.6.2 as development environment and as Target). Code uses an API method in core.runtime introduced in release after the Baseline all output set as error to ensure visible. This usage is not identified by the API tooling. Only identified by normal compiler error if Target platform is set to same as the Baseline. From reading the documentation, this is exactly the situation that API tooling should identify.

Also attempting to revert to not using the API Tooling ( reverted all .project to version prior to enabling API Tooling ) still gives error that Baseline is not set for workspace. Can API Tooling usage be undone.
Re: Unable to check API compatibility [message #765732 is a reply to message #765496] Wed, 14 December 2011 15:39 Go to previous message
Curtis Windatt is currently offline Curtis WindattFriend
Messages: 166
Registered: July 2009
Senior Member
The baseline should be the previous release (3.5) not 3.2.2. There shouldn't be a problem with using an API method from a later release as your target platform determines what dependencies you can have. API Tools checks that you are not using API illegally (accessing internals, @noextend, etc.) and that you are not modifying API in your projects without updating version numbers correctly.

Under the PDE Tools menu there is a menu option to remove API tools information from a project. Removing the nature from the .project or deleting the builder will turn off the builder for that project. The baseline error is set on the baselines preference page. Change that to ignore if you do not plan on using API Tools.
Previous Topic:unknown saveable assertation on reopening a custom editor
Next Topic:Getting project dependencies jars
Goto Forum:
  


Current Time: Fri Apr 19 01:46:05 GMT 2024

Powered by FUDForum. Page generated in 0.01861 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top