[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] Re: [eclipse-dev] Export-Package list: The plan
- From: Nick Edgar <Nick_Edgar@xxxxxxxxxx>
- Date: Wed, 13 Apr 2005 09:55:39 -0400
- Delivered-to: firstname.lastname@example.org
The component.xml file format is described here:
Note that this is not an OSGi or Eclipse runtime mechanism. The
component.xml files are taken as input to a separate validation tool run
at build time (i.e. a releng build, not as a builder within the IDE).
Sent by: equinox-dev-bounces@xxxxxxxxxxx
04/13/2005 09:25 AM
Please respond to
Equinox development mailing list
Glyn Normington <glyn_normington@xxxxxxxxxx>
[equinox-dev] Re: [eclipse-dev] Export-Package list: The plan
I believe that there is some doc for the component.xml stuff but am not
sure where it is. The x-internal and x-friends markup is "documented" in
04/13/2005 03:47 AM
Re: [eclipse-dev] Export-Package list: The planLink
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
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
Telephone: +44-(0)1962-815826. Email: glyn_normington@xxxxxxxxxx
Jeff McAffer <Jeff_McAffer@xxxxxxxxxx>
Sent by: eclipse-dev-bounces@xxxxxxxxxxx
Please respond to
"General development mailing list of the Eclipse project."
[eclipse-dev] Export-Package list: The plan
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
* 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
equinox-dev mailing list