You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "John Ross (JIRA)" <ji...@apache.org> on 2011/08/18 02:04:27 UTC
[jira] [Resolved] (ARIES-730) Generation of the osgi.identity
requirement must support version ranges.
[ https://issues.apache.org/jira/browse/ARIES-730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Ross resolved ARIES-730.
-----------------------------
Resolution: Fixed
> Generation of the osgi.identity requirement must support version ranges.
> ------------------------------------------------------------------------
>
> Key: ARIES-730
> URL: https://issues.apache.org/jira/browse/ARIES-730
> Project: Aries
> Issue Type: Bug
> Components: Subsystem
> Reporter: John Ross
> Assignee: John Ross
>
> An osgi.identity requirement is generated in order to retrieve resources from a Repository or Environment when, for example, provisioning content resources described in the Subsystem-Content or Deployed-Content manifest headers or transitive dependencies described in the Provision-Resource header. Because the Subsystem-Content header can include version ranges, the generation of the osgi.identity requirement must include support for converting a version range into a filter string.
> Ideally, I would like to use the new org.osgi.framework.VersionRange class described in RFC 175 targeted for core 4.4. This also includes support for distinguishing between development and release versions. An implementation is currently available within the OSGi Git repository at https://www.osgi.org/members/git/build.git under remote topic branch hargrave/version.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira