Yuna Morgenstern created MNG-6770:
-------------------------------------
Summary: Custom mojo changing project version but session doesn't
get updated
Key: MNG-6770
URL: https://issues.apache.org/jira/browse/MNG-6770
Project: Maven
Issue Type: Bug
Reporter: Yuna Morgenstern
I am using a custom maven plugin which helps me to preset the other plugins.
When I change my pom version (with org.codehaus.mojo:versions-maven-plugin:2.7)
and execute the maven-deploy-plugin afterwords, than the plugin is getting my
old version from somewhere in the session. As I am unable to debug through, it
would be great if someone could help me to fix this issue. where are these
properties coming from: "artifact", "projectArtifact", "finalName"
"project.build.finalName", "attachedArtifacts"...
Every plugin seems to work fine except the maven-deploy-plugin which is using
the project version from somewhere.
After versioning, I am changing the project in the MavenProject session as well
without success of effect for the next plugin. The only way is currently to run
my plugin twice. one for deployment and before everything else.
My application is doing following in order:
* Cleaning
* Resolving Plugins & Dependencies
* Updates Plugins & Dependencies
* Updates Project Semantic Version
* Compiles Main & Test
* Builds Javadoc
* Builds Sources
* Builds Artifact file
* Signs files with GPG
* Tagging
* Deployment
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
