Re: [Clirr-devel] CVS: clirr/core/src/java/net/sf/clirr/core/internal/checks InterfaceSetCheck.java,1.3,1.4

[<lak...@t-...>]

Vincent Massol wrote:

>  
>
>>-----Original Message-----
>>From: cli...@li... [mailto:clirr-devel-
>>ad...@li...] On Behalf Of Lars Kühne
>>Sent: samedi 21 août 2004 14:25
>>To: cli...@li...
>>Subject: Re: [Clirr-devel] CVS:
>>clirr/core/src/java/net/sf/clirr/core/internal/checks
>>InterfaceSetCheck.java,1.3,1.4
>>
>>Vincent Massol wrote:
>>
>>    
>>
>>>One more precision: I also got the following message in the console:
>>>
>>>[...]
>>>   [junit] Testsuite: org.apache.cactus.TestWebRequest
>>>   [junit] Tests run: 10, Failures: 0, Errors: 0, Time elapsed: 0,04 sec
>>>   [junit]
>>>java.lang.ClassNotFoundException: junit.framework.TestCase not found.
>>>java.lang.ClassNotFoundException: junit.framework.TestCase not found.
>>>java.lang.ClassNotFoundException: junit.framework.TestCase not found.
>>>java.lang.ClassNotFoundException: junit.framework.TestCase not found.
>>>java.lang.ClassNotFoundException: junit.framework.TestCase not found.
>>>java.lang.ClassNotFoundException: junit.framework.TestCase not found.
>>>java.lang.ClassNotFoundException: junit.framework.TestCase not found.
>>>java.lang.ClassNotFoundException: junit.framework.TestCase not found.
>>>java.lang.ClassNotFoundException: junit.framework.TestCase not found.
>>>java.lang.ClassNotFoundException: junit.framework.TestCase not found.
>>>java.lang.ClassNotFoundException: junit.framework.TestCase not found.
>>>java.lang.ClassNotFoundException: junit.framework.TestCase not found.
>>>java.lang.ClassNotFoundException: junit.framework.Test not found.
>>>
>>>BUILD FAILED
>>>java.lang.NullPointerException
>>>       at
>>>org.apache.bcel.classfile.JavaClass.getAllInterfaces(JavaClass.java:808)
>>>       at
>>>net.sf.clirr.core.internal.checks.InterfaceSetCheck.check(InterfaceSetChe
>>>      
>>>
>>ck.
>>    
>>
>>>java:58)
>>>
>>>So maybe there is some problem with the junit jar not being in some
>>>classpath?
>>>
>>>
>>>      
>>>
>>Yes, I'd guess that this is the result of the first issue I mentioned in
>>my other mail: dependencies are not considered (<[new/old]ClassPath>
>>subelements of the clirr Ant task)
>>
>>Any chance that you can add references to the same classpath that is
>>used for java compilation?
>>    
>>
>
>I'll check that. However, I still believe Clirr should not stop with a NPE.
>The error message should be better I think.
>
>  
>

I agree, but note that the NPE is thrown by BCEL, not by the clirr code 
- probably there isn't much we can do here...

Lars