The strange behavior of the dev server when using the GAE Plugin for Eclipse Indigo (3.7)

Good all the time of day!
Recently I started developing my first application on Google App Engine and instantly ran into a funny problem - the GAE server emulator included in the GAE SDK for Java refused to apply changes to the project code. Further description of the problem and how I got rid of it. Maybe it will save someone time.

Operational environment

There was a need to write your web application. Experience in such a matter is zero, but the main thing in our business is desire. Began to study the subject area. To develop from offsite, I downloaded the GAE SDK for Java and decided to rush into battle. But since the age at which I want to do everything from the command line, in order to get to the bottom of the very essence of what is happening has long passed, I decided to make my life easier with a bunch of Eclipse + GAE Plugin + GWT. I read the installation guide for this tool and decided to download the new Eclipse. I have a 64-bit system, Win 7. I downloaded two versions of IDE just in case (Eclipse Indigo), but it turned out that the 32-bit download ended faster. I installed the plug-in using the link dl.google.com/eclipse/plugin/3.7 (replacing the original 3.4 number from the tutorial with the version number of Indigo at your own risk) and created the first project using the plug-in, connecting the GAE Java SDK (there are only 32 -bit version).

Symptoms

For a while, everything went fine until debugging was needed directly. Gugloplagin allows you to run the server emulator directly from Eclipse by clicking on the corresponding debugging image. It was here that the jambs started - I change the project code (automatic build), I start the server, I go to localhost: 8080, and changes have happened. I begin to sin on the automatic assembly, turn it off, do the cleaning + manual assembly, the effect is the same. Stopping a one-time server restart (using a button in Eclipse) still causes changes in the project to start to appear in the browser. And the most interesting thing is to turn off Eclipse, and localhost still allows you to log in ... At the same time, the task manager does not display a separate server process, only the killing of javaw.exe helps.

Treatment

Decided to return to your favorite command line. Fortunately, the GAE SDK has a batch file for starting the server manually (it takes the port number and the path to the war directory as parameters). At the same time, I didn’t want to refuse to easily edit the project in Eclipse. I decided to edit the code in the IDE, and I wrote a script to start the server. The result - all changes in the code after rebuilding and restarting the server are instantly displayed in the browser. It was here that the thought of the compatibility of my 64-bit axis and the Eclipse + GAE Plugin bundle came to me (despite the fact that earlier applications in 32-bit Eclipse were developed quite successfully).
The result - running a 64-bit Eclipse + GAE Plugin with the same GAE Java SDK eliminated the problem with the development server (even the breakpoints work, the cool toy turned out).
')

Misadventure

Was lost all day. Unfortunately, the description of a similar problem with the head in ru (and not only ru) was not found by nete. So maybe someone will save time.