On which version does the cloud debugger takes snapshot.
Is it from default version?
if yes, how can I make it takes snapshot of some other version.
this page doesn't talks about versions.
If you have multiple versions (or modules) of the app deployed at the same time, the debugger UI (Google Developer Console --> Source Code --> Debug) will should a drop down. You can then choose the version and the module you want to debug.
Right -- Currently the debugger only works on the default version of the app engine app. You need to have the source code for that version of your app in the default branch of the git repo.
Related
The IDE complains about no Deployment selected, but from the picture I can't pick one.
I have upgraded IntelliJ to the latest. I am planning to reinstall everything.
Suggestions?
There should be an artifact displayed:
Make sure you have a war artifact defined in the Project Structure | Artifacts.
If the issue persists, please report a bug and attach a sample project to reproduce.
Artifact options available out of the box in IntelliJ IDEA Ultimate:
If you don't see the Web Application options, you need to make sure that all the plug-ins are enabled. You can also just delete disabled_plugins.txt file from the IDE CONFIG directory and restart the IDE.
In case you are still running into issues:
It actually looks like you are using the Cloud Tools for IntelliJ plugin (https://github.com/GoogleCloudPlatform/google-cloud-intellij) and not the App Engine plugin bundled in IDEA Ultimate as in the accepted answer.
You can refer to the following documentation for deployment to the App Engine standard environment:
https://cloud.google.com/tools/intellij/docs/deploy-std
Also a couple things to check:
You should have an app engine standard facet
You should have an exploded-war artifact:
Try the following action:
Tools > Google Cloud Tools > Add App Engine support > Google App Engine Standard and see if this resolves the problem.
If none of this helps, perhaps you can post some screenshots of your artifact / module structure under project settings.
So OK, at the end I was using IntelliJ Community which doesn't support deploying to Google App Engine anymore (although it's bizarre the plugin is available). Apparently one of the latest updates disable whatever minimal support was there, as I was able to deploy to GAE just a few weeks ago.
I'm trying to run an App Engine app locally using the development server, as specified in Google's docs. I'm running into a ton of compilation errors due to the go library packaged in the SDK missing system libraries.
Looking at the SDK download page, it says:
Note: The Google App Engine Launcher does not work with Go apps.
So is there no way to launch Go apps running on App Engine locally?
The GAE Go SDK contains and uses a modified version of Go 1.6.2., and the context package was added to the standard lib in Go 1.7. The old API that comes bundled in the SDK uses the appengine.Context context.
See related question: AppEngine/Go: Using a new version of Go with the SDK
Recently I've found out App Engine 1.9.1 has a bug which however does not occur in version 1.8.9 and below. I am developing my applications with Eclipse and the Google Plugin for Eclipse. In the Google properties of the project I switched back to 1.8.9. If I work locally I can see that it is using version 1.8.9 (the bug does not occur) however when I deploy to App Engine no matter what I do it will still run on 1.9.1. I even tryed to create a new project/application from scratch, still 1.9.1. I even deleted SDKs 1.9.1 and 1.9.0 from my system but nothing seems to help. What can I do? Thanks.
You don't control the version in production. It runs on Google servers and isn't deployed as part of your app.
Welcome to the cloud world where some parameters slip from your hand no matter how hard you try...
Indeed, you have no control over the AppEngine version that will be used to run your application in production. In fact, if you look carefully in the list of instance on your cloud console, you will see sometimes that some instances use an AppEngine version that is not even publicly available at the moment.
When I open my Eclipse, sometimes it shows App Engine is missing and I get several app engine errors. Why is it like I have to remove and add the app engine libraries again and again?
CAn u find the solution?
Check whether you are using an app engine of latest version or not. If you are using an old version please move to a new version 1.7.3 and check.
Question about getting the Java starter project booted up on Google App Engine
https://developers.google.com/glass/quickstart/java
In that quickstart when configuring Eclipse it says
Uncheck the Use Google App Engine checkbox and save.
However if I follow the instructions on the above page - including Eclipse with the Google plugin - I get a project which can be run on localhost. If I try to upload the App Engine it says this is not a App Engine project and won't upload.
So then if I make it one (go under the Google->App Engine settings) the Eclipse project complains about the jars under
web/WEB-INF/lib
and still won't upload. If I delete them then I get a project that doesn't compile either. So what do I need to do specifically to get this to load to the cloud?
Related to this is that I'm confused about the relationship between Maven and Eclipse - the two seem to be a cross purposes as Maven populates the lib directory but I keep wrangling with Eclipse over it too. The App Engine plugin seems to want to use it's jars, while the app-engine code I downloaded per the instructions (to get the bin utils app-cfg) want to be used too by Maven AFAIK.
Deploy to App Engine from the command line using appcfg.sh.
Getting many IDEs and App Engine to all work in the same project has led to some compromises due to differing assumptions made by each of the tools involved. For example, the Eclipse App Engine plugin makes different assumptions about the structure of projects than other IDEs. The compromise was to fall back to the official command line tools since they seem the most tolerant of variation and are always available.
Maven is part of the project to handle dependency management.
If you'd like to use Eclipse for your deployment too, you'll probably want to create a new Eclipse App Engine project and copy the libraries and code into that project.