Thanks for fixing it. Is there any way we can get a "build fixed" message from the MAVEN-BUILD server?
-Alex On 12/1/16, 6:23 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: >Ok ... so there was a locked file in the html modules target directory. >Sould be solved now ☺ > >Chris > >Am 01.12.16, 11:39 schrieb "Christofer Dutz" <christofer.d...@c-ware.de>: > > Having a look at this, it seems the agent went offline during one >build and after that there were problems cleaning up the html folder >after that. Eventually there’s still a process having a lock on a file in >there ... I’ll investigate the problem. > > Chris > > Am 01.12.16, 11:07 schrieb "carlos.rov...@gmail.com im Auftrag von >Carlos Rovira" <carlos.rov...@gmail.com im Auftrag von >carlosrov...@apache.org>: > > mmm that's strange...I have the build running localy. Maybe this >could be > some effect due to the server change ? > > 2016-12-01 9:55 GMT+01:00 Apache Jenkins Server ><jenk...@builds.apache.org>: > > > The Apache Jenkins build system has built FlexJS Framework >(maven) (build > > #447) > > > > Status: Still Failing > > > > Check console output at https://builds.apache.org/job/ > > FlexJS%20Framework%20(maven)/447/ to view the results. > > > > > -- > Carlos Rovira > http://about.me/carlosrovira > > > >
