[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Difference in system.packages.extra behaviour between 3.6.2 and 3.7

Hi Ben,

I tend to see this the other way aroundâ. if you are using that
package then you should have an Import-Package statement for it. If
that causes problems for PDE then that's a bug in PDE, not in Equinox.


On Thu, Sep 8, 2011 at 1:14 PM, Ben Cox <benjamin.cox@xxxxxxxxxx> wrote:
> Hi All,
> We're being affected by a difference between Equinox 3.6.2 and 3.7, and
> can't quite work out whether it's caused by a bug fix, a bug being
> introduced, or a change in the OSGi spec from 4.2 to 4.3.
> Our code has been converted to use OSGi and runs purely on IBM JVMs, and as
> such has dependencies on several IBM-specific packages of the JRE - for
> example, com.ibm.CORBA.iiop. To ensure these are exported from the JRE by
> the system bundle, we have added them to the
> org.osgi.framework.system.packages.extra property.
> We have set osgi.java.profile.bootdelegation=override and
> org.osgi.framework.bundle.parent=app.
> The problem is that at Equinox 3.6.2, our bundle is able to load a class
> from com.ibm.CORBA.iiop without adding it to the Import-Package statement.
> However, at 3.7, this is not possible. Instead, an Import-Package statement
> is required (which makes it tricky to compile in PDE...)
> Many thanks for your help,
> Ben
> ________________________________
> Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with number
> 741598.
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev