0

I'm using Google Plugin for Eclipse to deploy my app to GAE.

During "Deploy to Remote Server", console show me below error

95% Closing update: new version is ready to start serving.
98% Uploading index definitions.
99% Skipping dispatch.xml - consider running "appcfg.sh update_dispatch " or using the "--auto_update_dispatch" option

Update for module default completed successfully.

I tried run the command from GAE SDK (appcfg.cmd update...) from console, it is success. But deployment via Eclipse still having same error.

So alternative is to use "--auto_update_dispatch" option, may I know how can I enter that parameter in Eclipse?

enter image description here

songjing
  • 545
  • 4
  • 22
  • FWIW, that's just an info msg, not an error - the deployment is OK, just like your `update` SDK command. But note that you should use `update_dispatch` to update the dispatch config, not just `update` in that command. Which would be your workaround in case you can't find a way to configure the `--auto_update_dispatch` option in Eclipse (you'd update the dispatch config manually with that command - not a big deal - typically the dispatch config only changes rarely, like when you add/delete services to your app). – Dan Cornilescu Mar 19 '17 at 13:55
  • Hi. Thanks for the reply. I do go to command prompt, browse to the SDK folder where Eclipse refer to and run the command: appcfg.bat update_dispatch . That commond return success. However when I triggered the deploy to remote server from Eclipse plugin, warning still there. – songjing Mar 20 '17 at 23:59

1 Answers1

0

dispatch.xml should be in the default module under WEB-INF, mvn command won't update it so you have to do it manually via update_dispatch

other useful link

Khalil M
  • 1,788
  • 2
  • 22
  • 36
  • Hi. Thanks for the reply. I do go to command prompt, browse to the SDK folder where Eclipse refer to and run the command: appcfg.bat update_dispatch . That command return success. However when I triggered the deploy to remote server from Eclipse plugin, warning still there. – songjing Mar 21 '17 at 00:03
  • actually you should run it after you see the warning, but does it work? – Khalil M Mar 21 '17 at 00:14
  • That warning always display when I trigger deploy to remote server from Eclipse.
    I tried:
    [Run the update first] - Run the SDK update command from command prompt - Trigger the deployment from eclipse
    [Run the update after] - Run the SDK update command from command prompt - Trigger the deployment from eclipse
    When running SDK update command, it return success. But every time when trigger deployment from Eclipse, same warning display.
    I feel the update running on command prompt have nothing related to the deployment from Eclipse.     – songjing Mar 21 '17 at 02:57