I wonder if this has to do with tests being forked vs. not. When _not_ forked, then this would happen I am guessing. I am also guessing that something has changed in JUnit or Surefire. Perhaps all this needs is setting fork to true for tests that create the issue in the 1st place?
Gary On Sun, Apr 5, 2015 at 10:18 AM, Ralph Goers <[email protected]> wrote: > Oops. I just saw this thread. I am getting the same error and won’t be > able to perform a release until this is fixed. Anyone no what commit broke > it? > > Ralph > > > On Apr 5, 2015, at 8:27 AM, Gary Gregory <[email protected]> wrote: > > > > I think it has something to do with the fact that you cannot uninstall > our JUL layer or other layer so the wrong code is installed at some point > in the whole test suite. I am guessing it runs fine on its own. > > > > Gary > > > > > > -------- Original message -------- > > From: Remko Popma <[email protected]> > > Date: 04/05/2015 00:42 (GMT-08:00) > > To: Log4J Developers List <[email protected]> > > Subject: log4j-jul tests fail > > > > I am seeing this test for log4j-jul fail: > > > > java.lang.UnsupportedOperationException: Cannot set level through > log4j-api > > at > org.apache.logging.log4j.jul.ApiLogger.setLevel(ApiLogger.java:82) > > at > org.apache.logging.log4j.jul.CoreLoggerTest.testSetLevel(CoreLoggerTest.java:67) > > > > Did we do any work on JUL recently? (I can't find it in JIRA or > changes.xml) > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- 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
