Forum Controls
Spotlight Features

The Rich Engineering Heritage Behind Dependency Injection

Andrew McVeigh takes us on a tour of the rich heritage behind dependency injection, what it represents, and tells us why its here to stay.

Java, the OLPC, and community responsibility

The "One Laptop Per Child" project has a great device ready to ship, but there's no Java on there. Let's think about working together to put Java on OLPC!
Replies: 0 - Pages: 1  
Threads: [ Previous | Next ]
  Click to reply to this thread Reply

initializationError0 When Running JUnits Through Eclipse

At 4:28 PM on Aug 7, 2008, Ian Dees wrote:

Hi everyone,

On some of my JUnits that I run through Eclipse's JUnit interface
(alt-shift-x + t), I get an "initializationError0" as the only test, with
a Failure Trace of:

java.lang.VerifyError: (class: com/xx/yy/zzTest, method: unmarshall
signature: ([B[B)Lcom/xx/yy/zz;) Incompatible argument to function
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
at java.lang.Class.getConstructor0(Class.java:2699)
at java.lang.Class.getConstructor(Class.java:1657)
at junit.framework.TestSuite.getTestConstructor(TestSuite.java:177)
at junit.framework.TestSuite. (TestSuite.java:59)
at
org.junit.internal.runners.OldTestClassRunner. (OldTestClassRunner.java:23)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at
org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:27)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference. (JUnit4TestReference.java:28)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestClassReference. (JUnit4TestClassReference.java:24)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader.createTest(JUnit4TestLoader.java:40)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader.loadTests(JUnit4TestLoader.java:30)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:445)
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)

These tests are working on others' machines and on the build server, so
I'm convinced that it is my copy of Eclipse having the issue.

I'm running Version: 3.4.0, Build id: I20080617-2000.

Please forgive me if this is not the right place to ask a question, the
eclipse website is pretty unclear about where to go for a question like
this.

-Ian


thread.rss_message