v0.0.8

Fixed: Environment variables are not propagated to Docker during a build (as a result, .docker folder is created) (#65)
Fixed: Docker image build fails because Docker is not able to find Dockerfile (#60)
Feature: Stack deployment/destruction progress is not printed in the console if Maven batch mode is used (activated by -B or --batch-mode flags) (#55)

v0.0.7

Fixed: The deployment is considered completed if a stack is in UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS state (#29)
Fixed: The deployment order is incorrect if there're dependencies between stacks belonging to different environments (#32)
Feature: Add destroy goal to delete the deployed stacks (#34)
Feature: Add skip configuration property in order to allow conditional executions (#42)
Feature: Define property names to configure the plugin by means of system and project properties (#43)
Fixed: The plugin execution fails if a parameter value given in plugin configuration is null (#44)

v0.0.6

Fixed: The plugin execution fails with ClassCastException if a parameter default value is not String (#27)

v0.0.5

Feature: Add <arguments> parameter to pass arguments to the CDK application class (#26)

v0.0.4

Feature: Add the possibility to specify what stacks need to be deployed (#24)
Fixed: The plugin fails while reading cloud manifest (#22)
Fixed: The plugin fails with Maven 3.3.9 (#20)
Feature: Add the possibility to specify stack input parameters for the deployment (#18)

v0.0.3

Fixed: The deployment is considered successful if the deployment has been rolled back (#14)
Fixed: The plugin fails if a stack is in ROLLBACK_COMPLETE or ROLLBACK_FAILED before deployment (#16)

v0.0.2

Fixed: Synthesis fails if one of the stacks declares DynamoDB table (#12)
Fixed: An error message is shown twice if synthesis fails (#11)

Initial release

v0.0.1

chore: prepare release 0.0.1