You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-user@ant.apache.org by "Hiller, Dean (Contractor)" <de...@broadridge.com> on 2011/03/30 22:27:13 UTC
RE: ivyDE fails while ivy ant task succeeds? more info(packet snif...)
I found out it was asking for the *.sha file and I have no uploaded
checksum as we were having major problems with artifactory saying they
didn't match even though everything was working just fine so we disabled
it, but looks like IvyDE can't handle that maybe? For some reason ant
handles that situation fine.
So weird.
Dean
From: Hiller, Dean (Contractor)
Sent: Wednesday, March 30, 2011 2:15 PM
To: 'ivy-user@ant.apache.org'
Subject: ivyDE fails while ivy ant task succeeds?
This is very weird, but we have a dependency on a project oldDb version
1.0.+ from our main project.
This is a very consistent test case now....happens every time there is a
new deployment of oldDb project.
And when we do a Ivy->resolve in eclipse, it fails(but will pass in a
later step down below)!!!! The failure in eclipse is a popup window
with....
Some projects fail to be resolved
Impossible to resolve dependencies of com.broadridge#papr;1.0
download failed: com.broadridge#oldDb;1.0.6!oldDb-source.jar(source)
download failed: com.broadridge#oldDb;1.0.6!oldDb.jar
And when we run the ant build with SAME ivysettings.xml and same ivy.xml
file, it works AND gets the jars to the local cache on the computer at
which point I can then use Ivy->Resolve in eclipse and it will pass.
Is there something wrong with my ivysettings.xml file(though it works
via the ant task)...and why wouldn't IvyDE just be using the same code
that the ivy ant task is using(ie. It should not fail if the ant task is
not failing, right???)
<?xml version="1.0" encoding="UTF-8"?>
<ivy-settings>
<settings defaultResolver="main" />
<!--Authentication required for publishing (deployment). 'Artifactory
Realm' is the realm used by Artifactory so don't change it.-->
<credentials host="20.350.5.30" realm="Artifactory Realm"
username="admin" passwd="password"/>
<resolvers>
<chain name="main">
<ibiblio name="broadridge" m2compatible="true"
root="http://10.250.5.30:8081/artifactory/libs-release" />
<url name="artifactory-publish" m2compatible="true">
<artifact pattern=
"http://20.350.5.30:8081/artifactory/libs-release-local/[organization]/[
module]/[revision]/[artifact]-[revision].[ext]"/>
<ivy
pattern="http://20.350.5.30:8081/artifactory/libs-release-local/[organiz
ation]/[module]/[revision]/ivy-[revision].xml" />
</url>
</chain>
</resolvers>
</ivy-settings>
Thanks for any help on this,
Dean
This message and any attachments are intended only for the use of the addressee and
may contain information that is privileged and confidential. If the reader of the
message is not the intended recipient or an authorized representative of the
intended recipient, you are hereby notified that any dissemination of this
communication is strictly prohibited. If you have received this communication in
error, please notify us immediately by e-mail and delete the message and any
attachments from your system.
Re: ivyDE fails while ivy ant task succeeds? more info(packet snif...)
Posted by Nicolas Lalevée <ni...@hibnet.org>.
Look into your Ivy console [1], there will be probably more input about what is going wrong.
Nicolas
[1] http://ant.apache.org/ivy/ivyde/history/latest-milestone/console.html
Le 30 mars 2011 à 22:27, Hiller, Dean (Contractor) a écrit :
> I found out it was asking for the *.sha file and I have no uploaded
> checksum as we were having major problems with artifactory saying they
> didn't match even though everything was working just fine so we disabled
> it, but looks like IvyDE can't handle that maybe? For some reason ant
> handles that situation fine.
>
>
>
> So weird.
>
>
>
> Dean
>
>
>
>
>
>
>
> From: Hiller, Dean (Contractor)
> Sent: Wednesday, March 30, 2011 2:15 PM
> To: 'ivy-user@ant.apache.org'
> Subject: ivyDE fails while ivy ant task succeeds?
>
>
>
> This is very weird, but we have a dependency on a project oldDb version
> 1.0.+ from our main project.
>
>
>
> This is a very consistent test case now....happens every time there is a
> new deployment of oldDb project.
>
>
>
> And when we do a Ivy->resolve in eclipse, it fails(but will pass in a
> later step down below)!!!! The failure in eclipse is a popup window
> with....
>
>
>
> Some projects fail to be resolved
>
> Impossible to resolve dependencies of com.broadridge#papr;1.0
>
> download failed: com.broadridge#oldDb;1.0.6!oldDb-source.jar(source)
>
> download failed: com.broadridge#oldDb;1.0.6!oldDb.jar
>
>
>
> And when we run the ant build with SAME ivysettings.xml and same ivy.xml
> file, it works AND gets the jars to the local cache on the computer at
> which point I can then use Ivy->Resolve in eclipse and it will pass.
>
>
>
> Is there something wrong with my ivysettings.xml file(though it works
> via the ant task)...and why wouldn't IvyDE just be using the same code
> that the ivy ant task is using(ie. It should not fail if the ant task is
> not failing, right???)
>
>
>
> <?xml version="1.0" encoding="UTF-8"?>
>
> <ivy-settings>
>
> <settings defaultResolver="main" />
>
> <!--Authentication required for publishing (deployment). 'Artifactory
> Realm' is the realm used by Artifactory so don't change it.-->
>
> <credentials host="20.350.5.30" realm="Artifactory Realm"
> username="admin" passwd="password"/>
>
> <resolvers>
>
> <chain name="main">
>
> <ibiblio name="broadridge" m2compatible="true"
> root="http://10.250.5.30:8081/artifactory/libs-release" />
>
> <url name="artifactory-publish" m2compatible="true">
>
> <artifact pattern=
>
>
> "http://20.350.5.30:8081/artifactory/libs-release-local/[organization]/[
> module]/[revision]/[artifact]-[revision].[ext]"/>
>
> <ivy
> pattern="http://20.350.5.30:8081/artifactory/libs-release-local/[organiz
> ation]/[module]/[revision]/ivy-[revision].xml" />
>
> </url>
>
> </chain>
>
> </resolvers>
>
> </ivy-settings>
>
>
>
> Thanks for any help on this,
>
> Dean
>
>
> This message and any attachments are intended only for the use of the addressee and
> may contain information that is privileged and confidential. If the reader of the
> message is not the intended recipient or an authorized representative of the
> intended recipient, you are hereby notified that any dissemination of this
> communication is strictly prohibited. If you have received this communication in
> error, please notify us immediately by e-mail and delete the message and any
> attachments from your system.
>