Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [nebula-dev] Import-Package vs. Require-Bundle

Hi Hao,

Package-Versioning is a standard OSGi-Feature. You should find
informations about this in every OSGi-Book (e.g. Neil Bartlett's online
book discusses it)

Tom

Am 19.04.11 17:25, schrieb hao chen:
> Hi Tom,
>  
> What do you mean by 'bundles version their package'? Could you please
> provide an example to show how a bundle versions its packages?
>  
> 
> Best Regard
> 
> hao
> 
> 
> 
> ------------------------------------------------------------------------
> *From:* Tom Schindl <tom.schindl@xxxxxxxxxxxxxxx>
> *To:* Nebula Dev <nebula-dev@xxxxxxxxxxx>
> *Sent:* Tue, April 19, 2011 2:33:00 AM
> *Subject:* Re: [nebula-dev] Import-Package vs. Require-Bundle
> 
> Does CDT use Nebula? Looking at the feature list the RAP-Tooling is
> installed but I at least hope they did not install the runtime stuff.
> 
> If they do hold the RAP-runtime packages I think this can't even work
> because the then Eclipse itself would not resolve SWT and friends.
> 
> BTW ideally you are not developing against your IDE but an custom Target
> which should not hold the RAP-Fragments.
> 
> From an OSGi PoV using import-package is preferred BUT the problem still
> not solved by most upstream packages like SWT, JFace, ... is the
> versioning which makes using package imports a bit problematic because
> you can't define a version range.
> 
> As a rule of thumb I'd say:
> * use package imports if the upstream bundles version their package
>   (e.g. naturally all Equinox stuff does it)
> * use require-bundle if the upstream bundles are not versioning their
>   package (use optional require e.g. for RAP)
> 
> Tom
> 
> Am 19.04.11 00:13, schrieb Hannes Erven:
>> Folks,
>>
>>
>> I recently upgraded my workspace to 3.6.2 . Shortly(!) after that, I
>> cannot compile CDT anymore.
>>
>> The reason for this is that Eclipse started to satisfy the
>> org.eclipse.swt Import-Package by selected a RAP plugin instead of the
>> default SWT.
>> Unfortunately, that plugin has insufficent access granted and misses a
>> few fields, so CDT can't compile.
>>
>> As RAP is nowadays included in the default RCP and BIRT developer's
>> packages, I guess a few people will run into this.
>>
>>
>> Bug#214867 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=214867 )
>> argues in favor of Import-Package, but I had to change it back to
>> Require-Bundle locally to get things going again.
>>
>> Is there a proper way to resolve this, other than helping with the
>> development of RAP ;-] ?
>>
>>
>> Thanks!
>>
>> -hannes
>> _______________________________________________
>> nebula-dev mailing list
>> nebula-dev@xxxxxxxxxxx <mailto:nebula-dev@xxxxxxxxxxx>
>> https://dev.eclipse.org/mailman/listinfo/nebula-dev
> 
> _______________________________________________
> nebula-dev mailing list
> nebula-dev@xxxxxxxxxxx <mailto:nebula-dev@xxxxxxxxxxx>
> https://dev.eclipse.org/mailman/listinfo/nebula-dev
> 
> 
> 
> _______________________________________________
> nebula-dev mailing list
> nebula-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/nebula-dev



Back to the top