IssueTracker

The traditional mechanism for deploying Java web applications is by way of using a war file.  I believe that allowing the deployment of a war file (rather than its contents) would make automated build pipelines neater.  A war file is a neater build artifact that its exploded contents.  That war file should also be free from environment-specific settings.  I.e. The appengine-web.xml.

My build process should end with a (non-environment specific) war file.  My deployment process should take that war file and deploy it according to an (environment-specific) app.yaml.

Some companies have policies which mandate that an artifact must be deployed to lower environments before it (the exact same artifact) is allow into production.  Currently this is difficult to implement using GCP:

`mvn appengine:deploy` works directly from the source code
`mvn appengine:stage` produces a folder full of files (including appengine-web.xml) which must be changed per deployment