mailing list <equinox-dev@xxxxxxxxxxx>,
Some Packages must be imported outside of Eclipse
thanks for your answer.
If it's not recommend to change the property to make packages like
javax.* directly available: Is it possible in Eclipse to automatically
import such packages when I use classes from them? I want to avoid the
effort to manually check all my classes for imports from everything
except java.* and manually adding these packages to the bundle manifest
before I export the bundle as JAR.
-------- Original Message --------
Subject: Re: [equinox-dev] Some Packages must be imported outside of Eclipse
From: Richard S. Hall <heavy@xxxxxxxxxxxxxx>
To: Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
Date: Wed Jun 20 2012 22:26:55 GMT+0200
> On 6/20/12 16:17 , . wrote:
>> if I start a OSGi bundle in Eclipse (Equinox) not only java.*,
>> also packages like javax.* are directly available and therefore
>> be not imported in the bundle manifest.
> I would expect that you can import the javax.* packages, but you are
> correct that you shouldn't/can't import the java.* packages.
>> In contrast, when I run a bundle outside of Eclipse (also in Equinox;
>> with startup.bat/startup.sh and config.ini) all used packages
>> java.* MUST be imported, otherwise it results to Class Not Found
>> What is the reason why e.g. javax.* are not available outside
>> Eclipse without importing them? Is it possible, e.g. with a parameter
>> in the config.ini, to make these packages directly available or
>> other words create the same runtime environment like in Eclipse?
> The reason is historical, I'd guess.
> You can configure this via the org.osgi.framework.bootdelegation
> framework configuration property, but I'd recommend against doing
> Double check, but I'd expect that you can import the javax.* packages
> in Equinox when running in Eclipse...you should always import
> everything except java.* packages...
> -> richard
>> Thanks in advance!
>> equinox-dev mailing list
> equinox-dev mailing list