I am building trunk.  I have built it many times before and I am not doing 
anything differently, that I know of.  I checked 
http://repo1.maven.org/maven2/commons-httpclient/commons-httpclient/3.0/commons-httpclient-3.0.pom
 and it exists, but ivy.xml in ivy trunk is trying to access both a runtime and 
master configurations.  Where do those come from?  I don't see the word runtime 
or master in the pom.  Is this part of IVY's pom to ivy translation or 
something?  If I locally modify the ivy.xml so that it doesn't depend on the 
runtime or master configurations of commons-httpclient, it builds fine.  
Perhaps I am doing something wrong?

---
Shawn Castrianni


-----Original Message-----
From: Nicolas Lalevée [mailto:[EMAIL PROTECTED]
Sent: Monday, August 25, 2008 12:24 PM
To: [email protected]
Subject: Re: ivy compile problem


Le 25 août 08 à 18:04, Shawn Castrianni a écrit :

> [ivy:retrieve]
> [ivy:retrieve] :: problems summary ::
> [ivy:retrieve] :::: WARNINGS
> [ivy:retrieve]          ::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:retrieve]          ::          UNRESOLVED DEPENDENCIES         ::
> [ivy:retrieve]          ::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:retrieve]          :: commons-httpclient#commons-httpclient;
> 3.0: configuration not found in commons-httpclient#commons-
> httpclient;3.0: 'master'. It was req
> uired from org.apache.ivy#ivy;[EMAIL PROTECTED] default
> [ivy:retrieve]          ::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:retrieve]
> [ivy:retrieve]
> [ivy:retrieve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
>
> BUILD FAILED
>


BUILD SUCCESSFUL
Total time: 3 minutes 49 seconds

So, works for me, commons-httpclient 3.0 is correctly retrieved.
What are you building by the way? trunk ? tag ? some released sources ?

Nicolas

----------------------------------------------------------------------
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

Reply via email to