ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée (JIRA) <j...@apache.org>
Subject [jira] [Commented] (IVYDE-342) IvyDE requires newer version than Ivy provides
Date Sun, 31 Mar 2013 15:59:14 GMT

    [ https://issues.apache.org/jira/browse/IVYDE-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13618365#comment-13618365
] 

Nicolas Lalevée commented on IVYDE-342:
---------------------------------------

There is indeed something else going wrong with you use case. The version declared in the
feature.xml is the version of the bundle, not the packages. In OSGi world these version can
be different, as the implementation (bundle version) can evolves while the API does not (the
package version).
                
> IvyDE requires newer version than Ivy provides
> ----------------------------------------------
>
>                 Key: IVYDE-342
>                 URL: https://issues.apache.org/jira/browse/IVYDE-342
>             Project: IvyDE
>          Issue Type: Bug
>    Affects Versions: trunk
>            Reporter: Stephen Haberman
>
> In the Ivy project, the META-INF/MANIFEST.MF has:
> Export-Package: org.apache.ivy;version="2.0.0",
>  org.apache.ivy.ant;version="2.0.0"
> But in IvyDE, the feature.xml has:
> <import plugin="org.apache.ivy" version="2.1.0" match="compatible"/>
> So when I was building a local "ivyde.zip" file to use when our outstanding patches to
Ivy/IvyDE (via putting the jars into our ECLIPSE_HOME/dropins directory), OSGi could not start
IvyDE  because it's Ivy requirement couldn't be satisfied.
> After I changed Ivy's MANIFEST.MF to export version="2.4.0" (for all of the exported
packages), then it started working just fine.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message