When installing a new plugin on Eclipse 3.4, Eclipse checks for updates of all of that plugin's dependencies. This can take quite a while. To keep Eclipse from doing this overzealous update check, go to Help > Software Updates > Available Software > Manage Sites. You'll be presented with a list of Available Software Sites. Uncheck all of the update sites listed except for Google Plugin for Eclipse 3.4. At a later point, when you are interested in updating other components, check them again.
First, verify that your update site URL is correct for the version of Eclipse that you're using:
http://dl.google.com/eclipse/plugin/3.5
http://dl.google.com/eclipse/plugin/3.4
http://dl.google.com/eclipse/plugin/3.3
If you're sure that you typed the correct version, you may be behind a firewall that prevents Eclipse from reaching the update site (this is the case in some corporate environments). If there's a proxy server available, try configuring Eclipse to use the proxy via the instructions for Eclipse 3.5, Eclipse 3.4 or Eclipse 3.3. If you are still unable to reach the update site, you can try installing the Google Plugin for Eclipse from zip files.
Depending on the distribution of Eclipse you have, you may find no items checked by default. Just check the boxes next to Google Plugin for Eclipse and the bundled SDKs and click Finish.
If you're not using App Engine ORM in your project (for example, if you don't store any data on the server) you can turn off the DataNucleus Enhancer by right-clicking on your project and selecting Properties > Builders. Uncheck Enhancer. A confirmation dialog will appear; click OK to confirm that you want to disable the builder. You can turn it on again later if you start using ORM with your project.
The Eclipse IDE can sometimes have trouble detecting that code has been hot-swapped by the hosted mode infrastructure's ClassLoader, even though hosted mode's design guarantees that the code is correctly hot swapped on refresh. You can therefore safely ignore this dialog message if it comes up while refreshing code in the hosted mode browser.
If you discover that the code really wasn't refreshed in the hosted mode browser after seeing this hot code replacement error message, please let us know by filing an issue on the GWT Issue Tracker.
This problem occurs because the ORM enhancer process is invoked with the list of classes to be enhanced (by default, this is all classes in the project). If the command line to execute the enhancer is too long, Windows will prevent the execution of the process.
If your project is not using ORM, see the FAQ Entry "What is DataNucleus Enhancer? Can I turn it off?" to disable the enhancer.
If your project is using ORM, right-click on your project and choose Properties > Google > App Engine > ORM, and select only the files and folders of the classes which make use of ORM.
This is due to a difference between Java 1.5 and Java 1.6. As of Java 1.6,
the meaning of @Override has been extended to include implementing
a method defined in an interface, but doing this in Java 1.5 generates an
error. If you'd like to develop in the Java 1.5 style, just remove these
@Override annotations.
To use the Java 1.6 style, navigate to your workspace's JDK Compliance settings, under Window > Preferences > Java > Compiler (or Eclipse > Preferences on the Mac). Set Eclipse's "Compiler Compliance Level" to 1.6.
Both the local App Engine server and the deployment process need to run
javac in order to compile your JSPs. If your project isn't set to
use a JDK ("Java Development Kit", which includes
javac), then the JSPs can't be compiled.
Go to Preferences > Java > Installed JREs and make sure that you have a JDK installed -- if you don't, you can easily download one. Now right-click on your project and choose Properties > Java Build Path > Libraries and make sure that your project is using this JDK.
The bundled SDKs are in your Eclipse plugins directory,
underneath
com.google.gwt.eclipse.sdkbundle.platform_version for
GWT, and com.google.appengine.eclipse.sdkbundle_version
for App Engine.
The Google Plugin for Eclipse depends on other specific Eclipse components, such as WST. Your installation of Eclipse may not yet include all of them, but they can be easily installed by following these instructions.
|
http://download.eclipse.org/releases/galileo for the Location.
http://download.eclipse.org/releases/ganymede/
http://download.eclipse.org/releases/europa/If you activated Google SDKs for your project and then made a
war directory, the plugin will launch your application expecting
to find HTML pages in the public directory under GWT modules
instead of under war. To fix this, see the section on GWT 1.5
projects in Using Google Plugin
for Eclipse with existing projects.
This is a known issue with the current version of the plugin. In the meantime, you can work around it by removing your project from the Eclipse workspace: right-click the project, choose Delete, and click OK.
Warning: Make sure to leave the Delete project contents on disk box unchecked!
Now re-import your project by choosing File > Import > General > Existing Projects into Workspace.
These links should point your web browser to appspot.com, but on some systems, Eclipse may not be able to find your web browser. You can set which browser you would like to use by navigating to Preferences > General > Web Browser.
Not yet. For the initial release, we wanted to get you the plugin as fast as possible. However, we expect to make the source public in the near future.
You can uninstall the Google Plugin for Eclipse the same way you might uninstall any other Eclipse plugin. For Eclipse 3.5, go to Help > Install New Software..., and select the link for already installed. For Eclipse 3.4, go to Help > Software Updates > Installed Software. For Eclipse 3.3, go to Help > Software Updates > Manage Configuration. If you uninstall the plugin, you will have to uninstall the bundled SDKs first, which is done from the same dialog.
There are a number of ways you can contact the plugin team and other developers using Google Plugin for Eclipse. Check out the Community Resources page to find out how. We look forward to hearing from you!