db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kathey Marsden <kmarsdende...@sbcglobal.net>
Subject Re: Build Failed Error
Date Mon, 19 Apr 2010 18:07:49 GMT
On 4/17/2010 10:09 AM, Nirmal Fernando wrote:
> Hi All,
>
> Up to today I was able to compile and build derby from source without
> any problem. But suddenly I got an Build fail message, which I pasted
> below.
>
> BUILD FAILED
> C:\OtherNirmal\GSoC\Code\build.xml:1329: Unable to rename old file (C:\OtherNirm
> al\GSoC\Code\jars\sane\derby.jar) to temporary file
>
> So, I deleted all the jars inside sane and tried to build, and it was
> successful.
>    
I started seeing this in my environment when I moved from using classes 
in my classpath to  jars. This was a good switch to catch jar specific 
failures, but somehow it seemed the build was accessing the jars while 
trying to build them.  Since then I have been building with a script 
that removes the jars first before building them.  I  just   confirmed 
that I still see the error with my classpath if I do not remove the jars 
first.

.;C:\cygwin\svn4\trunk\jars\sane/derbyrun.jar;C:\cygwin\svn4\trunk\jars\sane\derbyTesting.jar;C:\cygwin\svn4\trunk\tools\java\junit.jar;C:\cygwin\svn4\trunk/tools/java/jakarta-oro-2.0.8.jar

I am not sure if this is a bug with the build or if you just have to do 
the cleanup first.  It would be nice if somehow the buildjars target 
could remove them first to avoid the error.





Mime
View raw message