Having issues deploying to app engine after my java 7 to 8 upgrade

[LeadWay Global]

I am running a multi-module java web application application.

Runs great under java7.  However, now that we are required to upgrade to java8 I updated my maven files and also the web files to use the java8 run time. 
All the steps when I exectute  mvn appengine:update, seems to run fine and the deploy seems to run fine however the old app (java 7) does not seem to shut down or the new ap does not start up. 

This is the logs I get: 

Beginning interaction for module default...

0% Created staging directory at: '/var/folders/5s/63hgymfs7js4tlx1zrpt12140000gn/T/appcfg4670965857950299255.tmp'

5% Scanning for jsp files.

8% Generated git repository information file.

20% Scanning files on local disk.

25% Scanned 250 files.

28% Initiating update.

31% Cloning 3 static files.

33% Cloning 362 application files.

40% Uploading 0 files.

52% Initializing precompilation...

90% Deploying new version.

95% Will check again in 1 seconds.

98% Will check again in 2 seconds.

99% Will check again in 4 seconds.

99% Will check again in 8 seconds.

99% Will check again in 16 seconds.

99% Will check again in 32 seconds.

99% Will check again in 60 seconds.

99% Will check again in 60 seconds.

99% Will check again in 60 seconds.

99% Will check again in 60 seconds.

99% Will check again in 60 seconds.

99% Will check again in 60 seconds.

99% Will check again in 60 seconds.

99% Will check again in 60 seconds.

99% Will check again in 60 seconds.

99% Will check again in 60 seconds.

99% Will check again in 60 seconds.

99% Will check again in 60 seconds.

99% Will check again in 1 seconds.

99% Will check again in 2 seconds.

99% Will check again in 4 seconds.

99% Will check again in 8 seconds.

99% Will check again in 16 seconds.

99% Will check again in 32 seconds.

99% Will check again in 60 seconds.

99% Will check again in 60 seconds.

99% Will check again in 60 seconds.

99% Will check again in 60 seconds.

99% Will check again in 60 seconds.

99% Will check again in 60 seconds.

99% Will check again in 60 seconds.

99% Will check again in 60 seconds.

99% Will check again in 60 seconds.

99% Will check again in 60 seconds.

99% Will check again in 60 seconds.

99% Will check again in 60 seconds.

99% Will check again in 60 seconds.

Sep 09, 2018 7:37:06 PM com.google.appengine.tools.admin.AppVersionUpload commit

SEVERE: Version still not serving, aborting.

99% Rolling back the update.

com.google.appengine.tools.admin.RemoteIOException: Version not ready.

Unable to update app: Version not ready.

Please see the logs [/var/folders/5s/63hgymfs7js4tlx1zrpt12140000gn/T/appcfg5707627753653038815.log] for further information.

It fails during the first module 'default' deploy.

On a side note where can I see what's inside that logs file?

On local, the java8 app runs fine.

[Linus Larsen]

Do you have the same version number on the app running as the one you have locally, if so one workaround can be to set another version number

on your local app. Run update, then enable the new version in the console UI. However, if everything works ok, remember to delete the instances of the

old version manually otherwise they will live and maybe affect your bill.

[Katayoon (Cloud Platform Support)]

I should add that as mentioned in the error message you can see the logs in the “/var/folders” path. Furthermore, you may use “--verbosity” flag set to debug for having more details on the deployment process. If the issue persists, I recommend to create a PRIVATE report in the Issue Tracker and provide us your project number to dig into the issue.    

[Julien Villegas]

Did you get to the bottom of this? I have the same issue:

Unable to update:

com.google.appengine.tools.admin.RemoteIOException: Version not ready.

projectID: crosswordbuildersweb.appspot.com

[Katayoon (Cloud Platform Support)]

Hi Julien,

If you are still getting this issue, you may report it via a PRIVATE report in the Issue Tracker and provide us your project number THERE, and more details on the steps you have taken to investigate the root cause of the issue.