[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Export-Package


Hi Scott,
Non-API packages should be marked as "x-internal" . In UI this can be done by going into Runtime tab of the manifest file, selecting a package, and setting "hidden from all plug-ins except". If you leave the list empty and save the file, the "x-internal" attribute will be generated.

The logic here is that contents of an "x-internal" package could be used as temporary way to get something not available through APIs. However, this is not something desirable so PDE will generate a warning saying that it is [much :-)] better to stick to APIs.  

This way full content of a plugin can be explored while keeping a clear distinction between APIs and non-APIs.  (All packages exported as "x-internal" or "x-friends" are not APIs.)

Sincerely,
Oleg Besedin



Scott Lewis <slewis@xxxxxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

11/04/2006 11:52 AM

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

To
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
cc
Erkki Lindpere <villane@xxxxxxxxx>
Subject
[equinox-dev] Export-Package





Hi Folks,

At the following URL:

http://wiki.eclipse.org/index.php/Export-Package

It says

   *  ALL Eclipse SDK plugins must list ALL of their packages in their
MANIFEST.MF files.
   * API or not. If you have a package on your plugin's classpath, it
must be listed.
   * New? List it! Old? List it! Borrowed from a friend? List it!

Is this convention appropriate for all other Eclipse projects?  Why
(particularly for *.internal.* packages) would this be a good idea for
new API?

Thanks for clarification,

Scott


_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev