[jira] [Resolved] (IVY-1208) OSGi-friendly OSGi friendly LatestRevisionStrategy

["Nicolas Lalevée (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IVY-1208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nicolas Lalevée resolved IVY-1208.
----------------------------------

       Resolution: Fixed
    Fix Version/s: trunk
         Assignee: Nicolas Lalevée

Actually now Bushel is part of Ivy. Hence the osgi-compatible lastest stragtegy is now at org.apache.ivy.osgi.core.OsgiRevisionStrategy. This will be part of Ivy 2.3 (even if it is in a quite experimental state for now).

Thanks for keeping this issue updated.

> OSGi-friendly OSGi friendly LatestRevisionStrategy
> --------------------------------------------------
>
>                 Key: IVY-1208
>                 URL: https://issues.apache.org/jira/browse/IVY-1208
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.0, 2.1.0, 2.2.0-RC1, 2.2.0
>            Reporter: John Gibson
>            Assignee: Nicolas Lalevée
>            Priority: Minor
>             Fix For: trunk
>
>         Attachments: osgi-friendly-latest-rev-strategy-aradeski.patch, separate-osgi-latest-rev-strategy.patch
>
>
> The latest revision strategy is incompatible with OSGi's versioning scheme.  For example 1.1.1 is considered to be after 1.1.1.foo.  This is at odds with OSGi's versioning rules, and can cause the incorrect revision to be selected when working with bundles from Spring Source's repository (http://www.springsource.com/repository/app/), for example.
> Alex Radeski raised this issue about 2 years ago and provided the attached patch to correct it. I propose that we either accept his patch to improve the behavior or follow Xavier Hanin's suggestion and adapt it to provide a separate osgi revision strategy.
> For the original discussion of the issue, see this discussion thread:
> http://marc.info/?l=ant-dev&m=122019942409967&w=1

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira