The error you are getting seems to be that the test can’t find the List appender - which is in the provided configuration.
I just built taglib with the current trunk again and had no problems. Ralph On Jun 17, 2014, at 6:33 AM, Gary Gregory <[email protected]> wrote: > On Tue, Jun 17, 2014 at 9:32 AM, Gary Gregory <[email protected]> wrote: > With the latest from trunk I now get these failures: > > Failed tests: > CatchingTagTest.testDoEndTag:76->verify:100 Missing Appender > CatchingTagTest.testDoEndTagLevelObject:94->verify:100 Missing Appender > CatchingTagTest.testDoEndTagLevelString:85->verify:100 Missing Appender > EntryTagTest.testDoEndTagAttributes:82->verify:88 Missing Appender > EntryTagTest.testDoEndTag:73->verify:88 Missing Appender > ExitTagTest.testDoEndTag:73->verify:95 Missing Appender > ExitTagTest.testDoEndTagResult01:81->verify:95 Missing Appender > ExitTagTest.testDoEndTagResult02:89->verify:95 Missing Appender > IfEnabledTagTest.testDoStartTagEnabledString:71 The return value is not > correct. expected:<1> but was:<0> > IfEnabledTagTest.testDoStartTagEnabledLevel:78 The return value is not > correct. expected:<1> but was:<0> > > LoggingMessageTagSupportTest.testDoEndTagMessageNoMarkerNoException:208->verify:301 > Missing Appender > > LoggingMessageTagSupportTest.testDoEndTagMessageNoMarkerException:234->verify:301 > Missing Appender > > LoggingMessageTagSupportTest.testDoEndTagMessageMarkerNoException:221->verify:301 > Missing Appender > > LoggingMessageTagSupportTest.testDoEndTagObjectMarkerException:293->verify:301 > Missing Appender > > LoggingMessageTagSupportTest.testDoEndTagStringMessageMarkerException:168->verify:301 > Missing Appender > > LoggingMessageTagSupportTest.testDoEndTagStringMessageNoMarkerException:156->verify:301 > Missing Appender > > LoggingMessageTagSupportTest.testDoEndTagStringMessageMarkerNoException:145->verify:301 > Missing Appender > > LoggingMessageTagSupportTest.testDoEndTagStringWithParameters:180->verify:301 > Missing Appender > > LoggingMessageTagSupportTest.testDoEndTagStringWithParametersMarkerAndException:195->verify:301 > Missing Appender > > LoggingMessageTagSupportTest.testDoEndTagMessageMarkerException:248->verify:301 > Missing Appender > > LoggingMessageTagSupportTest.testDoEndTagObjectNoMarkerNoException:259->verify:301 > Missing Appender > > LoggingMessageTagSupportTest.testDoEndTagObjectNoMarkerException:281->verify:301 > Missing Appender > > LoggingMessageTagSupportTest.testDoEndTagObjectMarkerNoException:270->verify:301 > Missing Appender > > LoggingMessageTagSupportTest.testDoEndTagStringMessageNoMarkerNoException:134->verify:301 > Missing Appender > > Tests run: 78, Failures: 24, Errors: 0, Skipped: 0 > > I should have added: > > [INFO] > ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] Apache Log4j 2 .................................... SUCCESS [0.535s] > [INFO] Apache Log4j API .................................. SUCCESS [11.226s] > [INFO] Apache Log4j Core ................................. SUCCESS [5:37.091s] > [INFO] Apache Log4j 1.x Compatibility API ................ SUCCESS [6.201s] > [INFO] Apache Log4j SLF4J Binding ........................ SUCCESS [4.433s] > [INFO] Apache Log4j to SLF4J Adapter ..................... SUCCESS [3.021s] > [INFO] Apache Log4j Commons Logging Bridge ............... SUCCESS [3.477s] > [INFO] Apache Log4j Flume NG Bridge ...................... SUCCESS [2:02.886s] > [INFO] Apache Log4j Tag Library .......................... FAILURE [9.091s] > [INFO] Apache Log4j JMX GUI .............................. SKIPPED > [INFO] Apache Log4j Samples .............................. SKIPPED > [INFO] Apache Log4j Samples: Flume - Common .............. SKIPPED > [INFO] Apache Log4j Samples: Flume - Remote .............. SKIPPED > [INFO] Apache Log4j Samples: Flume - Embedded ............ SKIPPED > [INFO] Apache Log4j 2 BOM ................................ SKIPPED > [INFO] Apache Log4j NoSQL Plugins ........................ SKIPPED > [INFO] Apache Log4j Web .................................. SKIPPED > [INFO] Apache Log4J Performance Tests .................... SKIPPED > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 8:20.397s > [INFO] Finished at: Tue Jun 17 09:17:16 EDT 2014 > [INFO] Final Memory: 52M/758M > [INFO] > ------------------------------------------------------------------------ > > Gary > > Gary > > > On Mon, Jun 16, 2014 at 11:55 PM, Ralph Goers <[email protected]> > wrote: > Yes, this is another case where simply running the unit tests would have > shown that the fix for LOG4J2-619 was bad as it caused all reconfigurations > to fail. Please stop being so quick to commit without testing. > > I fixed the problem. > > Ralph > > > > > > On Jun 16, 2014, at 6:27 AM, Matt Sicker <[email protected]> wrote: > >> This might be related to a bug fix patch I committed last night. I'll have a >> look when I get to work. >> >> On Monday, 16 June 2014, Ralph Goers <[email protected]> wrote: >> >> Failed tests: >> TestConfigurator.testReconfiguration:236 Configuration not reset >> FileConfigTest.testReconfiguration:62 Reconfiguration failed expected not >> same >> LoggerTest.testReconfiguration:210 Reconfiguration failed expected not same >> >> >> >> -- >> Matt Sicker <[email protected]> > > > > > -- > E-Mail: [email protected] | [email protected] > Java Persistence with Hibernate, Second Edition > JUnit in Action, Second Edition > Spring Batch in Action > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory > > > > -- > E-Mail: [email protected] | [email protected] > Java Persistence with Hibernate, Second Edition > JUnit in Action, Second Edition > Spring Batch in Action > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory
