https://answers.axonivy.com/questions/4310/supress-new-pmv-creation-when-deploying-with-project-build-plugin<p>I got a problem with Project Build Plugin, it creates new pvm all the time.</p> <p>do we have any option like redeploy=true to skip create new pvm?</p> <p>Thank you,</p> <p>Minh</p>enThu, 09 Jan 2020 03:00:34 -0500https://answers.axonivy.com/questions/4310/supress-new-pmv-creation-when-deploying-with-project-build-plugin/4311<p>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.</p> <p>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.</p> <p>However, <strong>with 8.0 LTS the developer has full control over the remote versioning</strong>: <a href="https://developer.axonivy.com/doc/latest/engine-guide/administration/deployment.html#versioning">https://developer.axonivy.com/doc/latest/engine-guide/administration/deployment.html#versioning</a></p> <p>Just provide a <code>deploy.options.yaml</code> with your versioning preference and the engine will comply with it. This can most easily be accomplished via a maven parameter: <a href="http://axonivy.github.io/project-build-plugin/release/8.0/deploy-to-engine-mojo.html#deployTargetVersion">http://axonivy.github.io/project-build-plugin/release/8.0/deploy-to-engine-mojo.html#deployTargetVersion</a></p>Reguel WermelingerThu, 09 Jan 2020 03:00:34 -0500https://answers.axonivy.com/questions/4310/supress-new-pmv-creation-when-deploying-with-project-build-plugin/4311