New PMVs will be automatically created if the version of your artifact in 'pom.xml' (Deployment) differs from the one deployed. Whenever you deploy a higher version the engine will also introduce a new PMV. In 7.0 one has to carefully maintain version of projects an be aware that it influences PMV versioning on the remote engine. And indeed, this is a show stopper if you prefer a strict maven versioning concept using released versions. Therefore, you have to find a compromise, e.g re-package your IAR for deployment or work with SNAPSHOT artifacts. However, **with 8.0 LTS the developer has full control over the remote versioning**: https://developer.axonivy.com/doc/latest/engine-guide/administration/deployment.html#versioning Just provide a `deploy.options.yaml` with your versioning preference and the engine will comply with it.it. This can most easily be accomplished via a maven parameter: http://axonivy.github.io/project-build-plugin/release/8.0/deploy-to-engine-mojo.html#deployTargetVersion

New PMVs will be automatically created if the version of your artifact in 'pom.xml' (Deployment) differs from the one deployed. Whenever you deploy a higher version the engine will also introduce a new PMV. In 7.0 one has to carefully maintain version of projects an be aware that it influences PMV versioning on the remote engine. And indeed, this is a show stopper if you prefer a strict maven versioning concept using released versions. Therefore, you have to find a compromise, e.g re-package your IAR for deployment or work with SNAPSHOT artifacts. However, with **with 8.0 LTS the developer has full control over the remote versioning: versioning**: https://developer.axonivy.com/doc/latest/engine-guide/administration/deployment.html#versioning Just provide a `deploy.options.yaml` with your versioning preference and the engine will comply with it.

New PMVs will be automatically created if the version of your artifact in 'pom.xml' (Deployment) differs from the one deployed. Whenever you deploy a higher version the engine will also introduce a new PMV. In 7.0 one has to carefully maintain version of projects an be aware that it influences PMV versioning on the remote engine. And indeed, this is a show stopper if you prefer a strict maven versioning concept using released versions. Therefore, you have to find a compromise, e.g re-package your IAR for deployment or work with SNAPSHOT artifacts. However, with 8.0 LTS the developer has full control over the remote versioning: https://developer.axonivy.com/doc/latest/engine-guide/administration/deployment.html#versioning Just provide a `deploy.options.yaml` with your versioning preference and the engine will comply with it.

New PMVs will be automatically created if the version of your artifact in 'pom.xml' (Deployment) differs from the one deployed. Whenever you deploy a higher version the engine will also introduce a new PMV. In 7.0 one has to carefully maintain version of projects an be aware that it influences PMV versioning on the remote engine.engine. And indeed, this is a show stopper if you prefer a strict maven versioning concept using released versions. Therefore, you have to find a compromise, e.g re-package your IAR for deployment or work with SNAPSHOT artifacts. However, with 8.0 LTS the developer has full control over the remote versioning: https://developer.axonivy.com/doc/latest/engine-guide/administration/deployment.html#versioning Just provide a `deploy.options.yaml` with your versioning preference and the engine will comply with it.

New PMVs will be automatically created if the version of your artifact in 'pom.xml' (Deployment) differs from the one deployed. Whenever you deploy a higher version the engine will also introduce a new PMV. In 7.0 one has to carefully maintain version of projects an be aware that it influences PMV versioning on the remote engine. However, with 8.0 LTS the developer has full control over the remote versioning: https://developer.axonivy.com/doc/latest/engine-guide/administration/deployment.html#versioning Just provide a `deploy.options.yaml` with your versioning preference and the engine will comply with it.