gradle-appengine-plugin | Gradle plugin that provides tasks | Build Tool library
kandi X-RAY | gradle-appengine-plugin Summary
kandi X-RAY | gradle-appengine-plugin Summary
NOTE: All App Engine users are encouraged to transition to the new gradle plugin for their projects. Android Studio users can migrate their projects using migration guide.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of gradle-appengine-plugin
gradle-appengine-plugin Key Features
gradle-appengine-plugin Examples and Code Snippets
Community Discussions
Trending Discussions on gradle-appengine-plugin
QUESTION
I am following a tutorial (https://github.com/GoogleCloudPlatform/gradle-appengine-plugin) on using google app engine to deploy from gradle. It say to point to your local installation of Google App Engine SDK. Except I don't really know how to find this, how would I find this?
...ANSWER
Answered 2019-Sep-17 at 23:00You are following an older tutorial. Please use the new tutorial for the new gradle plugin as your point of reference. The new tutorial does not require this information.
In regards to your question location of the SDK, it depends on the Operating System.
You can run the command gcloud info
which will detail about the installation. See Installation Properties
for more details about the install path.
QUESTION
After putting it off for a long time, I am finally updating from the gradle-appengine-plugin to the app-gradle-plugin. Although the documentation[1] calls for using an appengine-web file to configure the app, the plugin looks for an app.yaml configuration, which seems to be specific to the flexible environment. Does anyone have tips on either getting the plugin to use the appengine-web configuration, or configuring app.yaml for the standard environment? Thanks.
...ANSWER
Answered 2019-Jul-29 at 01:23It turns out that the problem was that the plugin does not use the appEngineDirectory
setting when looking for appengine-web.xml
. Instead, it looks for a app.yaml
file in that directory, and returns an error when it is not found (even if appengine-web.yaml
is there). If the appengine-web.xml
file is in the standard WEB-INF
folder, it works as expected.
I'll update if I can figure out how to use a custom directory for appengine-web.xml
.
QUESTION
I'm attempting to manipulate my Firebase database from Google App Engine. Having followed tutorials, I'm getting the following error -
java.lang.NoClassDefFoundError: Could not initialize class com.google.firebase.internal.FirebaseThreadManagers
Sometimes I see the following:
...
ANSWER
Answered 2017-Nov-30 at 20:11Don't use the firebase-admin dependency alongside the other Android client libraries in a server app. firebase-admin alone has everything you need to access Realtime Database in a JVM runtime. The Android client libraries will be of no use in a server app because they require Android infrastructure.
QUESTION
I'm trying to connect a backend module in Android Studio to Firebase using the tutorial here - https://cloud.google.com/solutions/mobile/firebase-app-engine-android-studio#adding_dependencies_to_the_backend_module
I cannot add the dependencies for some reason. I can't find them on the list. If I try to add them manually, I get a Gradle sync error.
For the main app module, Firebase is connected and it's functioning correctly. I set this up using Android Studio's build in Firebase tool. I've tried using this tool again but it's made no difference.
Here's my build.gradle for the backend:
...ANSWER
Answered 2017-Nov-28 at 20:53You're probably getting errors on these dependencies. They don't have versions specified:
QUESTION
When attempting to upgrade to Google Cloud Endpoints 2.0 using the gradle appengine plugin I run across a conflict with the configuration endpoints
. Gradle reports the error:
ANSWER
Answered 2017-Aug-10 at 12:42The problem occurs because the V2 endpoints-framework-gradle-plugin
and the gradle-appengine-plugin
both contain tasks named endpoints
. Removing the V2 plugin does not work, because the gradle-appengine-plugin
version does not support V2 Cloud Endpoints.
In the end, I had to migrate to the new appengine gradle plugin as suggested in the Android upgrade doc. This requires building and deploying from the command line and a custom task to handle JDO, but otherwise works fine.
QUESTION
I'm having trouble with reaching my Google Cloud Endpoints backend from my Android application. I use the following related tools and libraries:
- Android Studio 2.3
- Gradle plugin -
com.google.appengine:gradle-appengine-plugin:1.9.49
- App Engine SDK -
com.google.appengine:appengine-java-sdk:1.9.49
- Endpoints library -
com.google.appengine:appengine-endpoints:1.9.49
- Endpoints dependencies -
com.google.appengine:appengine-endpoints-deps:1.9.49
I've followed the documentation on testing with a physical device against the local development server, which means I've added the line httpAddress = "0.0.0.0"
to the build.gradle
in the backend module, and I connect to the backend using the following code:
ANSWER
Answered 2017-Mar-13 at 16:42Turns out that I copied the wrong IP-address from the ipconfig
-output, even though I mentioned I'm using the correct IP-address. Hrrm, embarassing...
After trying (what felt like) every possible solution, I once again checked the IP, and it turned out I'd copied the one labeled Default Gateway
, which was obviously not as correct as the one labeled IPv4 Address
!
So, if you're experiencing the same problem but still you feel like you've done everything correctly, make sure to double check the IP before giving up!
QUESTION
I have a Google App Engine project in Android Studio. In the past I have successfully deployed to my project to GAE many times. However, some project setting has changed and I can no longer deploy. I get the message:
...ANSWER
Answered 2017-Jan-24 at 17:29After lots of research, I have figured a fix. The library 'net.sargue:mailgun:1.0.0' apparently has a dependency of some sort on a java 8 lib (or something along those lines). I don't know why this hasn't caused me issues in the past, but it is now. Upgrading the lib to 'net.sargue:mailgun:1.3.2" resolves the issue.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install gradle-appengine-plugin
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page