Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Plugin Development Environment (PDE) » API Tooling: is no longer API
API Tooling: is no longer API [message #805262] Thu, 23 February 2012 09:59 Go to next message
Thorsten Meinl is currently offline Thorsten Meinl
Messages: 85
Registered: July 2009
Member
We have a plug-in that uses an external library as Jar and also exports
the packages of this external library. Now API Tooling complains about
classes in that library no longer being API even though absolutely
nothing changed in this plug-in compared to the baseline:

The type Jama.CholeskyDecomposition in org.knime.base_2.5.3 is no longer API
The type Jama.EigenvalueDecomposition in org.knime.base_2.5.3 is no
longer API
The type Jama.examples.MagicSquareExample in org.knime.base_2.5.3 is no
longer API
....

Is this a bug or am I doing something wrong?
Also, what exactly does "is no longer API" mean?

Thorsten
Re: API Tooling: is no longer API [message #805334 is a reply to message #805262] Thu, 23 February 2012 11:41 Go to previous messageGo to next message
Olivier Thomann is currently offline Olivier Thomann
Messages: 518
Registered: July 2009
Senior Member
Are you sure the manifest in these two jars is identical ?
Re: API Tooling: is no longer API [message #805346 is a reply to message #805334] Thu, 23 February 2012 11:53 Go to previous messageGo to next message
Thorsten Meinl is currently offline Thorsten Meinl
Messages: 85
Registered: July 2009
Member
Am 23.02.2012 17:41, schrieb Olivier Thomann:
> Are you sure the manifest in these two jars is identical ?
It's not exactly the same since one has been slightly modified during
the build process, but the relevant (?) entries such as Export-Package
and Bundle-Classpath are the same. What change in the manifest would
cause such an error message?
Re: API Tooling: is no longer API [message #805358 is a reply to message #805346] Thu, 23 February 2012 12:10 Go to previous messageGo to next message
Curtis Windatt is currently offline Curtis Windatt
Messages: 166
Registered: July 2009
Senior Member
My first thought was that the package was no longer public in the export-package header of the manifest. If it is marked as x-internal or x-friends it would no longer be considered API as it isn't publicly accessible.
Re: API Tooling: is no longer API [message #805376 is a reply to message #805358] Thu, 23 February 2012 12:32 Go to previous message
Thorsten Meinl is currently offline Thorsten Meinl
Messages: 85
Registered: July 2009
Member
We are not using any x-internal or x-friends attributes (yet).
Previous Topic:How to create preferences for my project nature
Next Topic:When is a class "API"?
Goto Forum:
  


Current Time: Fri Aug 22 13:54:10 EDT 2014

Powered by FUDForum. Page generated in 0.02863 seconds