Skip to main content

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

Hi Jeff,

Is there a write up of component.xml files and the use of "x-internal" and
"x-friends"? Presumably this is effectively a multi-bundle component model.

Do the rules below also apply to any OSGi bundles that may eventually be
shared between Eclipse and other OSGi platforms which don't have such a
component model? I would hope not.

(I kept this off the main eclipse-dev mailing list so as not to dilute your


Telephone: +44-(0)1962-815826. Email: glyn_normington@xxxxxxxxxx

             Jeff McAffer                                                  
   >                                                   To 
             Sent by:                  eclipse-dev@xxxxxxxxxxx             
             eclipse-dev-bounc                                          cc 
                                       [eclipse-dev] Export-Package list:  
             08/04/2005 20:55          The plan                            
             Please respond to                                             
              mailing list of                                              
                the Eclipse                                                

There is still some confusion around the Export-Package list in the
MANIFEST.MF.  Allow me to clarify the situation for all Eclipse SDK

*   ALL Eclipse SDK plugins must list ALL of their packages in their
*   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!

Exceptions to this model should be taken up with the PMC.

Notice that this puts us in exactly the same situation as we have always
been in.  Everyone has the ability to see everything.  As we have seen in
the past couple days, the community's desire/need for the freedom to access
non-API is overwhelming.  In fact, this forms a critical part of the
Eclipse ecosystem allowing experimentation and investigation.

This approach is NOT at odds with, and is fundamentally separate from, our
ongoing work to get control over the API and help developers stay on "the
right path".  That effort is supported by the addition of the component.xml
files, the use of "x-internal" and "x-friends" annotations on export
entries and the PDE/JDT work to more accurately model the runtime classpath
at development time.

All teams please review your Export-Package lists and ensure that all
packages are listed correctly.
eclipse-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit

Back to the top