| Problem with build after method signature change | Problem with build after method signature change 2007-08-03 - By billf5293
Thanks for the reply.
The reason we are doing these incremental builds is because unfortunately we
use very large applets containing a number of jars. One of the biggest
complaints we have about our product is the fact that downloading all these
jars after an update is time consuming. With these incremental builds only
the jars that need updating are touched allowing the client to use cached
jars for those jars that aren't updated.
Thanks.
Dominique Devienne-2 wrote:
>
> On 8/2/07, billf5293 <bfindeisen@(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: user-unsubscribe@(protected)
> For additional commands, e-mail: user-help@(protected)
>
>
>
--
View this message in context: http://www.nabble.com/Problem-with-build-after
-method-signature-change-tf4207673.html#a11982252
Sent from the Ant - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@(protected)
For additional commands, e-mail: user-help@(protected)
|
|
 |
