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

Jacob Certain updated IVYDE-363:
--------------------------------

    Description: 
One of my colleagues updated eclipse recently, which pulled in an Ivy 2.4 jar 
into `$ECLIPSE/plugins`. Thereafter, resolving a project in eclipse pops up 
this error:

{{The resolve job of ivy.xml\[*] in accountManagement has unexpectedly stopped}}
{{com/jcraft/jsch/agentproxy/AgentProxyException}}

Removing the ivy 2.4 jar from the eclipse plugin folder and replacing it with 
an ivy 2.3 jar fixed our problems.

  was:
One my colleagues updated eclipse recently, which pulled in an Ivy 2.4 jar into 
`$ECLIPSE/plugins`. Thereafter, resolving a project in eclipse pops up this 
error:

{{The resolve job of ivy.xml\[*] in accountManagement has unexpectedly stopped}}
{{com/jcraft/jsch/agentproxy/AgentProxyException}}

Removing the ivy 2.4 jar from the eclipse plugin folder and replacing it with 
an ivy 2.3 jar fixed our problems.


> Ivyde doesn't appear to work w/ ivy 2.4 and kepler
> --------------------------------------------------
>
>                 Key: IVYDE-363
>                 URL: https://issues.apache.org/jira/browse/IVYDE-363
>             Project: IvyDE
>          Issue Type: Bug
>          Components: workspace resolver
>    Affects Versions: 2.2.0.final
>         Environment: Eclipse Kepler SR2, fresh install
> Ant 1.9.3
> IvyDE 2.2.0 final, fresh install
> Ivy 2.3, manually installed (see description)
> Ivy 2.4 RC1, installed as part of IvyDE
>            Reporter: Jacob Certain
>              Labels: eclipse, ivy, ivyde
>
> One of my colleagues updated eclipse recently, which pulled in an Ivy 2.4 jar 
> into `$ECLIPSE/plugins`. Thereafter, resolving a project in eclipse pops up 
> this error:
> {{The resolve job of ivy.xml\[*] in accountManagement has unexpectedly 
> stopped}}
> {{com/jcraft/jsch/agentproxy/AgentProxyException}}
> Removing the ivy 2.4 jar from the eclipse plugin folder and replacing it with 
> an ivy 2.3 jar fixed our problems.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to