Eclipse Community Forums: Plugin Development Environment (PDE)

Help

Home

Home » Eclipse Projects » Plugin Development Environment (PDE) » API Tooling: is no longer API

Show: Today's Messages :: Show Polls :: Message Navigator

API Tooling: is no longer API [message #805262]

Thu, 23 February 2012 14:59

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

Report message to a moderator

Re: API Tooling: is no longer API [message #805334 is a reply to message #805262]

Thu, 23 February 2012 16:41

Olivier Thomann

Messages: 518
Registered: July 2009

Senior Member

Are you sure the manifest in these two jars is identical ?

Report message to a moderator

Re: API Tooling: is no longer API [message #805346 is a reply to message #805334]

Thu, 23 February 2012 16:53

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?

Report message to a moderator

Re: API Tooling: is no longer API [message #805358 is a reply to message #805346]

Thu, 23 February 2012 17:10

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.

Report message to a moderator