search

GoogleCloudPlatform / gradle-appengine-plugin

Gradle plugin that provides tasks for uploading, running and managing Google App Engine projects
Apache License 2.0
236 stars 60 forks source link

Endpoints support update? #261

Open loosebazooka opened 7 years ago

loosebazooka commented 7 years ago

http://stackoverflow.com/questions/39342980/migrating-to-cloud-endpoints-frameworks-2-0-for-app-engine#

gbhall commented 7 years ago

@loosebazooka can I please ask what the current status of this is? Cheers.

loosebazooka commented 7 years ago

um, we're not supporting the new tools with this older plugin. Support comes through

github.com/GoogleCloudPlatform/app-gradle-plugin github.com/GoogleCloudPlatform/endpoints-framework-gradle-plugin

gbhall commented 7 years ago

@loosebazooka Cheers man, I found this guide you wrote up which was perfect: https://github.com/GoogleCloudPlatform/endpoints-framework-gradle-plugin/blob/master/ANDROID_README.md

Unfortunately with so many changes (transitioning from v1), keeping track of all of this has been difficult.

So far seems so good, except I can no longer Deploy Module to App Engine due to Unable to find the webapp directory /Users/../PROJECTNAME/build/exploded-app, however I notice instead I have a exploded-PROJECTNAME folder instead. Still trying to solve that issue.

loosebazooka commented 7 years ago

So there's actually a little more to it than that. It looks like you're probably using Android Studio's deploy mechanism and the issue there is that, the tooling there doesn't sync with the new plugin. You're actually expected to use the gradle tooling directly to do things.

Some of this info is this guide : https://cloud.google.com/endpoints/docs/frameworks/legacy/v1/java/migrating-android

But basically for deploying you want to login using glcoud and then use ./gradlew appengineDeploy to do deployments.

For running, you would use ./gradlew appengineStart (non-blocking) instead of ./gradlew appengineRun(blocking) which will block the gradle daemon and Android Studio wont be happy

loosebazooka commented 7 years ago

I added some notes to the end of https://github.com/GoogleCloudPlatform/endpoints-framework-gradle-plugin/blob/master/ANDROID_README.md

gbhall commented 7 years ago

@loosebazooka that's really good info, cheers man. Noticed a typo long instead of longer for no long Gradle Sync fyi.

Only thing stopping me now is The Google Cloud SDK could not be found in the customary locations and no path was provided. My path is set, and using gcloud in terminal works as usual, so unsure why Android Studio is not picking it up. Will try a few more things, already tried rerunning ./google-cloud-sdk/install.sh.

gbhall commented 7 years ago

Reinstalled Google Cloud SDK, updated Android Studio, restarted mac, running which gcloud displays a path. Still getting The Google Cloud SDK could not be found in the customary locations and no path was provided. error.

It's 6am here, probably should call it a night. Thank you @loosebazooka so much for your help so far. Really been appreciated.