-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Application#compileJsps stopped working on Windows with 2.0.15 #25
Comments
I get this bug too: The error has been appearing since yesterday ( 06/28/2023 ) I did some research and realized that the error appears after the *.jsp module scans the appengineStage files: Beginning interaction for module default... After I tried to remove all *.jsp files and appengineStage was successful without errors, but *.jsp files are part of the project, what can I do ? Post it on stackoverflow and on github app-gradle-plugin Please help. can't deploy on production environment |
Thanks for the report.
We will upgrade to the newest guava, meanwhile, pin to the previous Cloud
CLI,
Ludo
…On Thu, Jun 29, 2023, 5:55 PM Step ***@***.***> wrote:
I get this bug too:
The error has been appearing since yesterday ( 06/28/2023 ) I did some
research and realized that the error appears after the *.jsp module scans
the appengineStage files:
*Beginning interaction for module default... 0% Scanning for jsp files. 0%
Compiling jsp files. Unable to stage app: 'posix:permissions' not supported
as initial attribute*
After I tried to remove all *.jsp files and appengineStage was successful
without errors, but *.jsp files are part of the project, what can I do ?
It doesn't matter what is in these files, the error appears even if you
put an empty *.jsp file in the directory webapp.
—
Reply to this email directly, view it on GitHub
<#25 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAATRTKVZ3RIFGMDYRTKWXDXNWQODANCNFSM6AAAAAAZXSCYYI>
.
You are receiving this because you are subscribed to this thread.Message
ID: <GoogleCloudPlatform/appengine-java-standard/issues/25/1613452400@
github.com>
|
Thank you very much, I'm waiting, the process is stopped, I can't deploy the application to Google cloud |
…uced in previous Guava version (#25) PiperOrigin-RevId: 544404346 Change-Id: Ibf1f3c6115b812fc33ffb47f174b848dcd92288f
The same issue! Waiting for the update 💯 |
@ludoch I tried downgrading to 436 but the same issue seems to occur. I even tried a really old version (copied the filestructure over to a different computer that was running 2xx) and it still happened. There must be some cached file somewhere. I'll try wiping all the cache/build folders and see if that helps but if not I might be at a loss. |
How did you move back to version 436?
See https://github.com/GoogleCloudPlatform/app-maven-plugin/blob/master/USER_GUIDE.md Also, since next week is 4rth of July US break, I do not expect a Cloud CLI release before the week after. |
Notes:
appengine {
tools {
cloudSdkVersion = '436.0.0'
}
} |
Thx. good workaround. I try from CLI gcloud components update --version=435.0.0 but it dont work |
Good call! This worked for me, thanks! I suppose the lack of version control in my gradle file is also what ultimately caused the biggest problems. |
Cloud SDK CLI has been updated and will be released next Tuesday. |
Hi, Going back to previous version is not working as expected. @ludoch when you mention next Tuesday, are you talking about 18th July? https://cloud.google.com/sdk/docs/release-notes Thanks. |
Going back to version 436.0.0 should work (see above thread for Maven or Gradle plugins) Fix will be in version of the week of 18th July |
Updated to the new version (438.0.0), the bug is still there and it prevents users from deploying. Google must be the only business willing to leave such a bug unfixed for this long. I am seriously considering moving to Azure or AWS; this is outrageous. |
The fix is in today's 439.0.0 (2023-07-18) build. |
After updating to gcloud 437.0.0 we started getting the following exception on Windows. It seems to have been introduced in guava 32.0.0 and fixed in guava 32.0.1.
The text was updated successfully, but these errors were encountered: