Frank Schönheit - Sun Microsystems Germany wrote:
Hi Stephan,
[...]
However, if you are willing to list unpublished API (at a level that
seems appropriate, like either a whole API or only individual types) in
extensions using it, you can leverage the extension dependency feature
introduced in OOo 2.0.4 (see
<http://specs.openoffice.org/appwide/packagemanager/extensiondependencies1.odt>):
For each version of an unpublished API, invent a dependency token. In
an extension that uses unpublished API, record the corresponding
dependencies. In OOo, specify those (and only those) dependencies as
fulfilled that correspond to the current versions of any unpublished API.
Interesting approach, but probably equally painful (and error-prone) to
maintain as manual type dependencies, on both the OOo and extension side.
The point is that this approach can be a little less painful and
error-prone than the approach of recording within an extension
information about each unpublished type used by that extension: The
designer of the unpublished API and the corresponding dependency tokens
decides on the granularity of how much of the API is covered by each
token. With very fine granularity (an individual token for each
individual API entity) recording the information is very painful, but
there will never be false positives of extensions that could still work
but are rejected. With very coarse granularity (a single token for the
complete API) recording the information is not very painful, but there
can potentially be lots of false positives.
-Stephan
[...]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
