Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Date: Wed, 1 Feb 2012 03:30:12 -0800 (PST)
From: Babak Vahdat <babak.vahdat@swissonline.ch>
To: dev@camel.apache.org
Message-ID: <1328095812358-5447239.post@n5.nabble.com>
In-Reply-To: 
 <CALvzYd_81omjnUZhG0YiJiv_V0MV9=731V+tvEOCWJx7HHYeSw@mail.gmail.com>
References: <1327746105060-5437720.post@n5.nabble.com>
 <CALvzYd_81omjnUZhG0YiJiv_V0MV9=731V+tvEOCWJx7HHYeSw@mail.gmail.com>
Subject: Re: [FOLLOW UP] - Recent Build failures on Windows
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi

interestingly the again-and-again-repeating Maven issue on Windows:

Caused by: java.io.IOException: Failed to delete
F:\hudson\hudson-slave\workspace\Camel.trunk.fulltest.windows\camel-trunk\camel-core\target\camel-core-2.10-SNAPSHOT.jar

did *not* happen anymore by the last build of today morning, so that the
behaviour is to my understanding non-deterministic:

https://builds.apache.org/job/Camel.trunk.fulltest.windows/231/console

I've got no clue which "zombie" process or what exactly inhibits Maven to
delete that jar (from time to time) which happened again by the previous two
builds:

https://builds.apache.org/job/Camel.trunk.fulltest.windows/230/console
https://builds.apache.org/job/Camel.trunk.fulltest.windows/229/console

Babak

--
View this message in context: http://camel.465427.n5.nabble.com/FOLLOW-UP-Recent-Build-failures-on-Windows-tp5437720p5447239.html
Sent from the Camel Development mailing list archive at Nabble.com.