Maven Plugin for Azure App Service default to primary artifact
For the Maven Plugin for Azure App Service, the resource section of the deployment configuration in the POM should default to the primary artifact of the POM, in the case where the primary artifact is a war. This is the obvious default that Java programmers would expect. Deploying a war is the most typical use case for this plugin. Maven knows where the primary artifact is, so configuring a directory would be unnecessary. In a POM Maven properties are available for the primary artifact. Maven plugins are expected to be aware of the primary artifact. As it is, configuring this plugin requires us to repeat ourselves in the most typical use case in terms of specifying the primary artifact of the POM.
Hanxiao Liu commented
@Hugh Thanks for your idea, maven plugin will auto detect artifact in build directory in V1 schema with war/jar deploy, you may find the document here (https://github.com/microsoft/azure-maven-plugins/blob/azure-webapp-maven-plugin-1.9.0/azure-webapp-maven-plugin/v1-schema.md#deployment-settings).
For v2 schema, please specify the artifact location in <resources>, but you could use `mvn azure-webapp:config` to generate new configuration with default resource settings, which could fit the primary artifact.