ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacob Certain (JIRA)" <>
Subject [jira] [Commented] (IVY-1471) Can't resolve with ivyde, ivy 2.4, and eclipse kepler
Date Fri, 16 May 2014 11:22:34 GMT


Jacob Certain commented on IVY-1471:

Forgive my ignorance, but all the jars in the ivy bin-with-deps tarball show up in eclipse
as part of my ant path. And when I use ant on the command line, there are no issues. Casting
a wider net for exceptions sounds like a decent workaround since you say it works, but I'm
still not understanding the discrepancy between using ant/ivy/ivyde with eclipse and ant/ivy
out of eclipse.

You wrote "jsch-agent jar", I'm assuming (hoping) that was an abbreviated reference to all
the jsch agent proxy jars, since the ivy-with-deps tarball doesn't have a jar with that name.
It'd be super dumb if I'm just missing one last jar.

Btw, the tarball I'm using is: apache-ivy-2.4.0-rc1-bin-with-deps.tar.gz

> Can't resolve with ivyde, ivy 2.4, and eclipse kepler
> -----------------------------------------------------
>                 Key: IVY-1471
>                 URL:
>             Project: Ivy
>          Issue Type: Bug
>    Affects Versions: 2.4.0-RC1
>         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
>            Assignee: Nicolas Lalevée
>              Labels: eclipse, ivy, ivyde
>             Fix For: trunk
>         Attachments: ivyde resolve exception.txt
> 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

View raw message