I have seen this locally. I saw this yesterday but I've not tried building today.
Gary On Sun, Feb 21, 2016 at 10:36 AM, Remko Popma <[email protected]> wrote: > Does anyone have this problem also? > > PropertiesRoutingAppenderTest.routingTest Could not delete > target\routing1\routingtestProps-Alert.log, last modified 2/22/16 1:16 AM > RoutingAppenderTest.routingTest Could not delete > target\routing1\routingtest-Alert.log, last modified 2/22/16 1:16 AM > RoutingAppenderWithPurgingTest.routingTest Could not delete > target\routing-purge-idle\routingtest-3.log, last modified 2/22/16 1:16 AM > RoutingDefaultAppenderTest.routingTest Could not delete > target\routing1\routingtest.log, last modified 2/22/16 1:16 AM > > > I changed it to use the java.nio.file API, now the error message says: > PropertiesRoutingAppenderTest.routingTest > java.nio.file.FileSystemException: > target\routing1\routingtestProps-Alert.log: The process cannot access the > file because it is being used by another process. > > > This is a parameterized test with two @Rules. Could they interfere? (I'm > not very familiar with this way of JUnit testing.) > -- E-Mail: [email protected] | [email protected] Java Persistence with Hibernate, Second Edition <http://www.manning.com/bauer3/> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> Spring Batch in Action <http://www.manning.com/templier/> Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
