Unable to deploy to Tomcat 10.0 using azure-webapp-maven-plugin 2.12.0

[mores]

Plugin name and version

azure-webapp-maven-plugin
2.12.0

Plugin configuration in your pom.xml

<plugin>
                                <groupId>com.microsoft.azure</groupId>
                                <artifactId>azure-webapp-maven-plugin</artifactId>
                                <version>2.12.0</version>
                                <configuration>
                                        <appName>alerts</appName>
                                        <region>eastus</region>
                                        <resourceGroup>alerts</resourceGroup>
                                        <runtime>
                                                <os>Linux</os>
                                                <javaVersion>Java 11</javaVersion>
                                                <webContainer>Tomcat 10.0</webContainer>
                                        </runtime>
                                        <deployment>
                                                <resources>
                                                        <resource>
                                                                <directory>${project.basedir}/target</directory>
                                                                <includes>
                                                                        <include>*.war</include>
                                                                </includes>
                                                        </resource>
                                                </resources>
                                        </deployment>
                                </configuration>
                        </plugin>

Expected behavior

Tomcat 10 is running on Java 11

Actual behavior

Tomcat 8.5.85 is running on Java 8

Steps to reproduce the problem

mvn clean package azure-webapp:deploy

[Flanker32]

@mores Thanks a lot for your report and sorry for the late response. It seems that there are some updates in app service runtime stack. We will fix this issue soon, and will update here once we got any updates.

As a workaround, you may set the runtime in portal manually. Here is the screenshot