It seems the line causing this error is:
throw new SurefireExecutionException(
e.getTargetException().getMessage(), e.getTargetException() );
Frankly, I don't see how the target exception can have an abstract
method at all. According to the docs an AbstractMethodError only
happens when the class definition changed at runtime, meaning the
class was already instantiated when it was changed to be abstract.
This is either a corrupt class, or an illegal class.
If you have it available, try recompiling Surefire, changing the above
line to read:
System.err.println("GOT EXCEPTION: " +
e.getTargetException() + " / " +
e.getTargetException().getClass().getName());
e.getTargetException().printStackTrace(System.err);
throw new SurefireExecutionException(
e.getTargetException().getMessage(), e.getTargetException() );
This will give you more information on which class is causing this.
Quintin Beukes
On Tue, Oct 13, 2009 at 7:13 PM, Quintin Beukes <[email protected]> wrote:
> Did you perhaps switch JDK version?
>
> Quintin Beukes
>
>
>
> On Tue, Oct 13, 2009 at 5:37 PM, Benson Margulies <[email protected]>
> wrote:
>> java.lang.AbstractMethodError:
>> java.lang.Throwable.getMessage()Ljava/lang/String;
>> at
>> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:353)
>> at
>> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
>>
>>
>> This 'just started happening.' No additional info from -X.
>>
>> maven version is 2.2.1.
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
