Plugin watches the wrong application when more then one application has the same name

[ullgren]

When more than one application (deployment) has the same name and one of them is deployed to runtime fabcric there is a chance that the mule maven plugin will wait for the wrong deployment to become ready.

This scenario is possible when you have two applications with the same name in the same environment and one of the applications are on a runtime fabric and the other is on a standalone server. This will result in a faulty timeout when since the expected deployment status for a runtime fabric application will never occur when the mule maven plugin checks the status of the stand alone application.

Reproduce

• Make sure to have one stand alone server and a runtime fabric cluster in the same environment
• Create a new application names "echo" deploy it to one of the standalone server
• Using the mule maven plugin deploy the same application with the same application name ("echo") to the runtime fabric cluster.
• Even if the deployment is successful the mule maven plugin will timeout since it tries to track the deployment on the standalone server.

Expected result

The mule maven plugin should verify that it is tracking the deployment it just created, not just a deployment with the same name.

Reference to code:
https://github.com/mulesoft/mule-maven-plugin/blob/2.x/mule-deployer/src/main/java/org/mule/tools/verification/fabric/RuntimeFabricDeploymentVerification.java#L71
https://github.com/mulesoft/mule-maven-plugin/blob/3.x/mule-deployer/src/main/java/org/mule/tools/verification/fabric/RuntimeFabricDeploymentVerification.java#L79

[ullgren]

Compare how the ArmClient find the application id taking target id into consideration

https://github.com/mulesoft/mule-maven-plugin/blob/3.x/mule-deployer/src/main/java/org/mule/tools/client/arm/ArmClient.java#L217-L222