Ugh. I just found out I've been running Wicket 1.2 tests all the time. In my version of Eclipse, there is a bug that if you change the project of an already defined runner, it'll 'change' that without complaints, but when you run it, it'll still use the old one. Darn. Now the errors in Eclipse and maven are the same. Sorry.
Eelco On 10/16/06, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
With V2 there are overall 4 failing tests as well, which are failing for other reasons. 3 are related to wicket:component and one is called ScopedHeader.... Ignore these errors for now. Does maven show the same errors or different one? Juergen On 10/15/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > That bug is fixed now too. What remains is that from eclipse all tests > run fine, but from maven, several fail (2 failures, 4 errors). > > Eelco > > > On 10/15/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > The loop is fixed. What - again - drives me crazy though is that these > > tests work fine in Eclipse but fail with maven. > > > > Eelco > > > > > > On 10/15/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > > Fixed. > > > > > > On 10/15/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > > > Great. Indeed, with maven there is a loop. > > > > > > > > > > > > On 10/15/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > > > > For the record, I didn't really change the initializer code, but for > > > > > 1.2 I added a project, wicket-jmx, which has a wicket.properties file > > > > > and an initializer, and for 2.0 I added the jmx code in the core > > > > > project itself, and added that initializer call to the already > > > > > existing inititializer. I can see from the stacktrace that you've been > > > > > testing 2.0. It should be perfectly legal to add an initializer like > > > > > that though, and we've done that before without troubles too. > > > > > > > > > > Eelco > > > > > > > > > > > > > > > > > > > > On 10/15/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > > > > > Interesting... I don't get such exceptions, nor do I get that loop. I > > > > > > test from Eclipse. You? > > > > > > > > > > > > Eelco > > > > > > > > > > > > > > > > > > On 10/15/06, Juergen Donnerstag <[EMAIL PROTECTED]> wrote: > > > > > > > Once I fixed the endless loop I got > > > > > > > > > > > > > > wicket.WicketRuntimeException: > > > > > > > javax.management.InstanceAlreadyExistsException: > > > > > > > wicket.app.WicketTester:type=Application,name=ApplicationSettings > > > > > > > at wicket.jmx.Initializer.init(Initializer.java:97) > > > > > > > at wicket.Initializer.init(Initializer.java:51) > > > > > > > at wicket.Application.initialize(Application.java:808) > > > > > > > at wicket.Application.initializeComponents(Application.java:831) > > > > > > > at wicket.Application.initializeComponents(Application.java:577) > > > > > > > at wicket.protocol.http.WicketFilter.init(WicketFilter.java:344) > > > > > > > at wicket.protocol.http.MockWebApplication.<init>(MockWebApplication.java:148) > > > > > > > at wicket.util.tester.WicketTester.<init>(WicketTester.java:205) > > > > > > > at wicket.WicketTestCase.setUp(WicketTestCase.java:62) > > > > > > > at junit.framework.TestCase.runBare(TestCase.java:125) > > > > > > > at junit.framework.TestResult$1.protect(TestResult.java:106) > > > > > > > at junit.framework.TestResult.runProtected(TestResult.java:124) > > > > > > > at junit.framework.TestResult.run(TestResult.java:109) > > > > > > > at junit.framework.TestCase.run(TestCase.java:118) > > > > > > > at junit.framework.TestSuite.runTest(TestSuite.java:208) > > > > > > > at junit.framework.TestSuite.run(TestSuite.java:203) > > > > > > > at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128) > > > > > > > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > > > > > > > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) > > > > > > > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) > > > > > > > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) > > > > > > > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) > > > > > > > Caused by: javax.management.InstanceAlreadyExistsException: > > > > > > > wicket.app.WicketTester:type=Application,name=ApplicationSettings > > > > > > > at com.sun.jmx.mbeanserver.RepositorySupport.addMBean(RepositorySupport.java:452) > > > > > > > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1410) > > > > > > > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:936) > > > > > > > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:337) > > > > > > > at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:497) > > > > > > > at wicket.jmx.Initializer.init(Initializer.java:68) > > > > > > > ... 21 more > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 10/15/06, Juergen Donnerstag <[EMAIL PROTECTED]> wrote: > > > > > > > > Did someone recently change the initializer code? It seems like it is > > > > > > > > causing endless loops with the junit tests > > > > > > > > > > > > > > > > Juergen > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
