He he ;) Not sure yet. The new failure is in FactoryFinderTest, but the only change to the code was in UIComponentTestCase, which is now a child of AbstractJsfTestCase.
Inside the failing test of FactoryFinder, the test calls FactoryFinder.getFactory(FactoryFinder.APPLICATION_FACTORY) and is getting back shale's MockApplicationFactory (which is placed there from a previous test, the recently changed UIComponentTestCase). This happens even though FactoryFinder.releaseFactories() is called in FactoryFinderTest.tearDown() . Dennis Byrne >-----Original Message----- >From: Wendy Smoak [mailto:[EMAIL PROTECTED] >Sent: Sunday, February 19, 2006 10:27 PM >To: 'MyFaces Development' >Subject: Re: [continuum] BUILD FAILURE: API > >On 2/19/06, [EMAIL PROTECTED] ><[EMAIL PROTECTED]> wrote: >> Online report : >> http://myfaces.zones.apache.org:8080/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/34/buildId/511 >> Build statistics: >> State: Failed >... >> [INFO] snapshot struts:shale-test:1.0.1-SNAPSHOT: checking for updates from >> apache-maven-snapshots >... >> [surefire] Tests run: 9, Failures: 1, Errors: 0, Time elapsed: 0.01 sec >> <<<<<<<< FAILURE !! >> [surefire] Running javax.faces.convert.DateTimeConverterTest >> [surefire] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.003 sec >> <<<<<<<< FAILURE !! > >I updated the Shale snapshots about half an hour ago... coincidence? > >-- >Wendy >
