app-gradle-plugin breaks tasks in multi project build? #1005
Comments
|
Are you building a project with an appengine-web.xml or just an app.yaml? Also can you include all of the exception, it's hard to determine much from the truncated error message? |
|
The appengine-web.xml is based off this example but changed to Java 11: Here is the full stacktrace I get when I use --stacktrace: |
|
The error seems to be coming from around here. I don't really get why it causes the error. (Maybe Looking at the code, one workaround to avoid getting into the error line is to not use a "managed Cloud SDK." ("Managed" means app-gradle-plugin automatically downloads an SDK at some cache location (e.g., This way, I was able to make the example run. |
It's quite possible. The task apis in this project are a little on the older side, we don't really do any task configuration avoidance (https://docs.gradle.org/current/userguide/task_configuration_avoidance.html) |
This will be a little tricky for me right now since I'm on NixOS and its currently not possible but that's a me problem. I may have to wait until GoogleCloudPlatform/app-gradle-plugin#394 is finished. |
|
I'm afraid GoogleCloudPlatform/app-gradle-plugin#394 will be in a draft state for a considerable amount time.
I'm not saying you should install |
|
To clarify, the NixOS issue is only when using the package manager. You'll not hit the issue with |
|
Thank you for the clarification. My expectation was that it would not be able to run the downloaded version since downloaded executables sometime do no work on NixOS as I've encountered with things like Gradle managed NPM before. Thankfully the downloaded gcloud sdk can in fact run. I can confirm that adding the following to my build.gradle.kts has fixed it for now: I appreciate the assistance. |
|
Should I close this issue since I have a workaround and GoogleCloudPlatform/app-gradle-plugin#394 is tracking the underlying fix? |
|
For tracking purposes, we use a GitHub issue, so we want this issue to remain open. (#394 is a PR.) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I want to use the frontend-gradle-plugin with this plugin.
If I start with the multi-project-war-application example from the fronend-gradle-plugin everything builds fine.
When I add the app-gradle-plugin using either the method in the documentation the build the fails. For example if I add it through a build script block:
Gradle will fail with:
Note that in the example project the build.gradle has the following part:
After adding the app-gradle-plugin the dependsOn line fails. Through debugging I've found that project(':frontend').tasks becomes empty after the app-gradle-plugin is added.
What is the app-gradle-plugin doing that is changing tasks in the project? Is there a different way I can look up the assembleFrontend task that will work with the app-gradle-plugin or is the plugin fundamenatally incompatible with multi project gradle builds?
The text was updated successfully, but these errors were encountered: