[jira] [Commented] (IVYDE-342) IvyDE requires newer version than Ivy provides

["Stephen Haberman (JIRA)" <ji...@apache.org>]

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

Stephen Haberman commented on IVYDE-342:
----------------------------------------

What is very odd is that I cannot explain why this only started breaking for me now--a month or so ago, I used the same approach to make an ivyde.zip file that worked fine. It's almost like Eclipse had been ignoring the version issue. Not really sure.

Either way, it seems safe to bump Ivy's "export version" up to 2.4.0?
                
> 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