Re: [GUMP@vmgump]: Project ant-contrib (in module ant-contrib) failed

Curt Arnold <[email protected]> Wed, 1 Aug 2007 11:14:59 -0500
Newsgroups gmane.comp.java.ant-contrib.devel
Message-ID <[email protected]>
On Aug 1, 2007, at 5:11 AM, Gump Integration Build wrote:

>
> init:
>
> configure:
> [ivy:configure] Loading jar:file:/srv/gump/public/workspace/ant- 
> contrib/lib/ivy/jars/ivy-1.4.1.jar!/fr/jayasoft/ivy/ivy.properties
> [ivy:configure] :: Ivy 1.4.1 - 20061109165313 :: http:// 
> ivy.jayasoft.org/ ::
> [ivy:configure] :: configuring :: file = /srv/gump/public/workspace/ 
> ant-contrib/ivy-conf.xml
>
> resolve:
> [ivy:resolve] :: resolving dependencies :: [ sourceforge | ant- 
> contrib | working@vmgump ]
> [ivy:resolve] 	confs: [default, provided, test]
> [ivy:resolve] 	found [ apache | bcel | 5.1 ] in local
> [ivy:resolve] 	found [ apache | commons-httpclient | 3.0.1 ] in local
> [ivy:resolve] 	found [ apache | commons-logging | 1.0.4 ] in local
> [ivy:resolve] 	found [ jayasoft | ivy | 1.4.1 ] in local
> [ivy:resolve] 	found [ apache | ant | 1.6.5 ] in local
> [ivy:resolve] 	found [ apache | xercesImpl | 2.6.2 ] in local
> [ivy:resolve] 	found [ junit | junit | 3.8.1 ] in local
>
> BUILD FAILED
> /srv/gump/public/workspace/ant-contrib/build.xml:43: impossible to  
> resolve dependencies: java.io.FileNotFoundException: /home/ 
> gump/.ivy/cache/[email protected]  
> (Permission denied)
>
> Total time: 1 second
> ---------------------------------------------
>
> To subscribe to this information via syndicated feeds:
> - RSS: http://vmgump.apache.org/gump/public/ant-contrib/ant-contrib/ 
> rss.xml
> - Atom: http://vmgump.apache.org/gump/public/ant-contrib/ant- 
> contrib/atom.xml
>


That doesn't look right.  With the -Dno-ivy set, the configure and  
resolve targets should be no-ops.  The size for build.xml in http:// 
vmgump.apache.org/gump/public/ant-contrib/ant-contrib/gump_file/ 
list_source_ant-contrib.html is 9455 while in the current SVN HEAD it  
is 11789 (all the other file sizes match) which makes me think that  
Gump was running with a stale snapshot.  Another Gump run is in  
progress if that doesn't fix it, then maybe need to blow away the  
current Gump checkout and see if a fresh checkout helps.



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/