Yes, the first thing to do when a "curious" problem occurs is doing
a "clean build".
ant clean build
Provide a "clean" target which deletes all generated files.
Jan
>-----Ursprüngliche Nachricht-----
>Von: Dominique Devienne [mailto:[EMAIL PROTECTED]
>Gesendet: Donnerstag, 2. August 2007 20:56
>An: Ant Users List
>Betreff: Re: Problem with build after method signature change
>
>On 8/2/07, billf5293 <[EMAIL PROTECTED]> wrote:
>>
>> We are experiencing a problem with our build after a method
>signature change
>> in one of our classes. A method was changed from non-static
>to static.
>> Since the dependant class files would still compile ant did
>not compile
>> them. The result is a IncompatibleClassChangeError at
>runtime saying a
>> non-static method is expected.
>>
>> Is there any way to check class compatibility?
>
>It's generally regarded as unnecessary, since Java compiles fast
>enough that doing a full rebuild is much simpler and safer than trying
>to do an intelligent incremental build.
>
>There are IDEs and also JavaMake that do such incremental builds, and
>I played with JavaMake in the past, but the added complexity is not
>worth it IMHO. It all depends on the project size. --DD
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
