I just migrated my project to 1.6.4. Now whenever I make even the most unsignificant change to any of my UI-classes I get: 'Hot Code Replace failed' when debugging in eclipse, and have to reload my application. This was not the case in 1.5.3.
I have tried to narrow down the problem, as it is possible to succeed with hot code replace under very simple circumstances. The problem seems to be related to local class defintions, specifically unnamed classes. As it is the case in 1.5.3, one would expect the replace only/mostly to fail when introducing new members or methods. Does anyone have a solution or an explanation for why the 1.6.4 verson is so inferior to 1.5.3 on this point? I am seriously considering migrating back to 1.5. Regards Lasse --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
