[news.eclipse.tools] Re: [plugin.xml] i can't understand the usage of "e

["Joseph Khalil" <joseph_khalil@xxxxxxxxxxx>]

i guess that's right in export element under the library element
its documented as

Each <library> element can specify which portion of the library should be
exported. The export rules are specified as a set of export masks. By
default (no export rules specified), the library is considered to be private

but what about the export attribute in the export attribute in the import
element
it's documented as

a.. export - specifies whether the dependent plug-in classes are made
visible (are (re)exported) to users of this plug-in. By default, dependent
classes are not exported (are not made visible)

but i can't understand it


"Christophe Elek" <celek@xxxxxxxxxx> wrote in message
news:Xns92FD9ECDD74CFcelekcaibmcom@xxxxxxxxxxxxxxxx
> Jared Burns <jared-eclipse@xxxxxxxxx> wrote in
> news:avhv39$4j1$1@xxxxxxxxxxxxx:
>
> > I hope I'm not spreading false information here, but my understanding
> > is that export makes things available automatically to plugins that
> > require you. If a plugin lists your plugin as a dependency, it will
> > automatically get the exported libraries listed in your plugin.xml -
> > it won't have to explicitly require them in *it's* plugin.xml.
> >
> > - Jared
>
> my understanding is that if plug-in A require classes from plug-in B then
>
> plugin.XML A must require plugin id B
> AND
> B must export the classes A wants to use
>
> --
> Christophe Elek
> Eclipse Project
> http://www.eclipse.org