2.3.0RC1 experimental OSGI dependencies - revision ranges

[Hlg Tschr]

Hi,

I played around with the experimental OSGI feature of the release
candidate and got stuck with inter-bundle dependencies. I am using
org.eclipse.emf.ecore rev 2.7.0.v20110605-0747, which gets resolved
properly with a revision of 2.7.+ specified in the ivy file. Another
dependent bundle specifies the required revision range as
[2.7.0,3.0.0) in its manifest, which is not resolved. This may be
related to the different notation of exclusive ranges in OSGI bundles
and ivy files. I think the revision range should be converted to a
range of [2.7.0,3.0.0[ to be resolved by ivy correctly?

Cheers,

Hlg

[Nicolas Lalevée]

Le 27 avr. 2012 à 16:17, Hlg Tschr a écrit :

> Hi,
>
> I played around with the experimental OSGI feature of the release
> candidate and got stuck with inter-bundle dependencies. I am using
> org.eclipse.emf.ecore rev 2.7.0.v20110605-0747, which gets resolved
> properly with a revision of 2.7.+ specified in the ivy file. Another
> dependent bundle specifies the required revision range as
> [2.7.0,3.0.0) in its manifest, which is not resolved. This may be
> related to the different notation of exclusive ranges in OSGI bundles
> and ivy files. I think the revision range should be converted to a
> range of [2.7.0,3.0.0[ to be resolved by ivy correctly?

The version range should be correctly interpreted. If you interested in reading some code, see VersionRange#toIvyRevision() [1]. Something else is probably going wrong.

Nicolas

[1] http://svn.apache.org/repos/asf/ant/ivy/core/trunk/src/java/org/apache/ivy/osgi/util/VersionRange.java

[Hlg Tschr]

Yes, version ranges are perfectly ok. I didn't declare the proper
latest strategy for the OBR resolver. Sorry for the confusion. Hlg

2012/4/28 Nicolas Lalevée <nicolas.lalevee@...>:

>
> Le 27 avr. 2012 à 16:17, Hlg Tschr a écrit :
>
>> Hi,
>>
>> I played around with the experimental OSGI feature of the release
>> candidate and got stuck with inter-bundle dependencies. I am using
>> org.eclipse.emf.ecore rev 2.7.0.v20110605-0747, which gets resolved
>> properly with a revision of 2.7.+ specified in the ivy file. Another
>> dependent bundle specifies the required revision range as
>> [2.7.0,3.0.0) in its manifest, which is not resolved. This may be
>> related to the different notation of exclusive ranges in OSGI bundles
>> and ivy files. I think the revision range should be converted to a
>> range of [2.7.0,3.0.0[ to be resolved by ivy correctly?
>
> The version range should be correctly interpreted. If you interested in reading some code, see VersionRange#toIvyRevision() [1]. Something else is probably going wrong.
>
> Nicolas
>
> [1] http://svn.apache.org/repos/asf/ant/ivy/core/trunk/src/java/org/apache/ivy/osgi/util/VersionRange.java