I would propose the following:
Index: lucene/build.xml
===================================================================
--- lucene/build.xml (revision 1395520)
+++ lucene/build.xml (working copy)
@@ -546,8 +546,8 @@
<!-- NOTE: not really useful anymore ... -->
<target name="clean-jars" description="Clean local jars">
- <delete failonerror="false">
- <fileset dir="." includes="**/*.jar"/>
+ <delete>
+ <fileset dir="." includes="**/*.jar" excludes="build/**"/>
</delete>
</target>
Index: solr/build.xml
===================================================================
--- solr/build.xml (revision 1395520)
+++ solr/build.xml (working copy)
@@ -677,8 +677,8 @@
<!-- NOTE: not really useful anymore -->
<target name="clean-jars" description="Clean local jars">
- <delete failonerror="false">
- <fileset dir="." includes="**/*.jar"/>
+ <delete>
+ <fileset dir="." includes="**/*.jar" excludes="build/**"/>
</delete>
</target>
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: [email protected]
> -----Original Message-----
> From: Uwe Schindler [mailto:[email protected]]
> Sent: Monday, October 08, 2012 1:47 PM
> To: [email protected]
> Subject: RE: [JENKINS] Lucene-Solr-trunk-Windows (64bit/jdk1.7.0_07) - Build #
> 1084 - Failure!
>
> The clean-jars task should only remove ivy-jars! Shouldn't it exclude
> **/build/*
> Then this problem would be solved... I don't like the failOnError=false. I
> sometimes call ant clean-jars and I am happy that it throws BuildException
> when I have the JAR file or any other (if ant clean) file open e.g. in ZIP
> window.
>
> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: [email protected]
>
>
> > -----Original Message-----
> > From: Robert Muir [mailto:[email protected]]
> > Sent: Monday, October 08, 2012 1:39 PM
> > To: [email protected]
> > Subject: Re: [JENKINS] Lucene-Solr-trunk-Windows (64bit/jdk1.7.0_07) -
> > Build #
> > 1084 - Failure!
> >
> > Its really not interesting, its just the first one in alphasort order.
> >
> > On Mon, Oct 8, 2012 at 7:38 AM, Uwe Schindler <[email protected]> wrote:
> > > The interesting thing is that this only happens on *this* single JAR file.
> > >
> > > -----
> > > Uwe Schindler
> > > H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de
> > > eMail: [email protected]
> > >
> > >
> > >> -----Original Message-----
> > >> From: Michael McCandless [mailto:[email protected]]
> > >> Sent: Monday, October 08, 2012 1:03 PM
> > >> To: [email protected]
> > >> Subject: Re: [JENKINS] Lucene-Solr-trunk-Windows (64bit/jdk1.7.0_07)
> > >> - Build #
> > >> 1084 - Failure!
> > >>
> > >> Do we know what's causing these false failures...? Something is
> > >> holding a JAR file still open, when "ant clean-jars" tries to remove it?
> > >>
> > >> Is there some workaround...?
> > >>
> > >> Mike McCandless
> > >>
> > >> http://blog.mikemccandless.com
> > >>
> > >> On Sun, Oct 7, 2012 at 10:30 PM, Policeman Jenkins Server
> > >> <jenkins@sd- datasolutions.de> wrote:
> > >> > Build:
> > >> > http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Windows/10
> > >> > 84/
> > >> > Java: 64bit/jdk1.7.0_07 -XX:+UseG1GC
> > >> >
> > >> > All tests passed
> > >> >
> > >> > Build Log:
> > >> > [...truncated 27369 lines...]
> > >> > BUILD FAILED
> > >> > C:\Users\JenkinsSlave\workspace\Lucene-Solr-trunk-
> > Windows\build.xml:245:
> > >> The following error occurred while executing this line:
> > >> > C:\Users\JenkinsSlave\workspace\Lucene-Solr-trunk-Windows\lucene\bu
> > >> > ild
> > >> > .xml:552: Unable to delete file
> > >> > C:\Users\JenkinsSlave\workspace\Lucene-Solr-trunk-Windows\lucene\bu
> > >> > ild \analysis\common\lucene-analyzers-common-5.0-SNAPSHOT.jar
> > >> >
> > >> > Total time: 57 minutes 2 seconds
> > >> > Build step 'Invoke Ant' marked build as failure Archiving artifacts
> > >> > Recording test results Description set: Java: 64bit/jdk1.7.0_07
> > >> > -XX:+UseG1GC Email was triggered for: Failure Sending email for
> > >> > trigger: Failure
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > -------------------------------------------------------------------
> > >> > -- To unsubscribe, e-mail: [email protected] For
> > >> > additional commands, e-mail: [email protected]
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: [email protected] For
> > >> additional commands, e-mail: [email protected]
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [email protected] For
> > > additional commands, e-mail: [email protected]
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected] For additional
> > commands, e-mail: [email protected]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
