Hi equinox-dev team,
I have a question regarding exporting an unversioned package.
If I look over the bundles in eclipse, the most of them (expect of some orbit
bundles) exports packages without a version.
We do it likewise e.g.:
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: Xbase
This is a common misconception. There is no connection between bundle version
and exported package versions. A bundle that imports using Import-Package will
only care about the exported package versions, and a bundle that requires using
Require-Bundle will only care about the Bundle-Version.
Si
equinox-dev-boun...@eclipse.org wrote on 2014/12/11 09:08:19:
> From: Dennis Hübner
> To: equinox-dev@eclipse.org
> Date: 2014/12/11 09:10
> Subject: [equinox-dev] Exporting packages without a version
> Sent by: equinox-dev-boun...@eclipse.org
>
> Hi equinox-dev team,
&
365 to have p2 detect the
need to refresh older versions of a bundle when installing new ones.
Tom
From: Dennis Hübner
To: equinox-dev@eclipse.org
Date: 12/11/2014 08:10 AM
Subject:[equinox-dev] Exporting packages without a version
Sent by:equinox-dev-boun...@eclip
Hi Neil,
thanks for your answer.
That means, that if a consumer bundle imports any packages but defines a
requier-bundle with a version constraint to 2.8.0 it may became
classes loaded from a bundle with version 2.7.3? At least the console shows me
that both versions are wired.
We also have Linka
It’s very unusual and wrong for a bundle to both import a package with
Import-Package AND require the exporting bundle with Require-Bundle. Both of
these requirements will be wired up independently, and will result in a highly
inconsistent class space that is the reason for your LinkageErrors et
symbolic name when p2 installs and resolves/refreshes the new
> versions. I am pretty sure that if you ran with -clean this strange wiring
> situation would disappear. I have opened p2 bug
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=449365
> <https://bugs.eclipse.org/bugs/show_
From: Neil Bartlett
To: Equinox development mailing list
Date: 12/11/2014 08:45 AM
Subject:Re: [equinox-dev] Exporting packages without a version
Sent by:equinox-dev-boun...@eclipse.org
It’s very unusual and wrong for a bundle to both import a package with
Import
> Date:12/11/2014 08:45 AM
> Subject: Re: [equinox-dev] Exporting packages without a version
> Sent by:equinox-dev-boun...@eclipse.org
>
>
>
> It’s very unusual and wrong for a bundle to both import a package with
> Import-Package AND require the exp
gt;> To: Equinox development mailing list > <mailto:equinox-dev@eclipse.org>>
>> Date:12/11/2014 08:45 AM
>> Subject:Re: [equinox-dev] Exporting packages without a version
>> Sent by:equinox-dev-boun...@eclipse.org
>> <mailto:e
list
Date: 12/11/2014 09:08 AM
Subject:Re: [equinox-dev] Exporting packages without a version
Sent by:equinox-dev-boun...@eclipse.org
Hi Tom, yes I’m aware of that, however if there are different sets of
packages exported by the two versions then you may get visibility of some
11 matches
Mail list logo
