Users need to be able to make continuous changes and testing those changes without deleting the container manually.

[Cristiano] Current behaviour doest not target a continuous build and deploy of the same project version, which I agree for this use case it becomes time consuming. It could add a third option in case a container with same name exists, allowing the usee to ovewrite it( delete and recreate )?

[Kris] In general we do advice to up the version (GAV) and deploy a new container.

[Cristiano] If you up the GAV version it will deploy a new container ( leaving the old one intact ). Perhaps we could consider recreating the same container only for -SNAPSHOT versions. If there is container if the same GAV for that snapshot, we could automatically remove and create a new one. In terms of quick testing fixes, it would avoid having to bump the version up for everytime the user needs to deploy something.

• Automatically recreate containers for SNAPSHOT project builds