In this example, I just trying to force the change of the version from 0.0.1-SNAPSHOT to 1.0.0.
The jar file name and it contents is created correct (ex. my-project-1.0.0.jar) but when the deploy goal starts, it deploy the JAR with the old name (my-proejct-0.0.1-SNAPSHOT.jar) on my maven distribution repository.
I'm not sure there is a really good answer to this. Mutation of the project model like this is certainly not going to behave very well. Any reason why the maven-release-plugin doesn't work for you?
I'm trying to create a dynamic version control using a groovy script like this:
In this example, I just trying to force the change of the version from 0.0.1-SNAPSHOT to 1.0.0.
The jar file name and it contents is created correct (ex. my-project-1.0.0.jar) but when the deploy goal starts, it deploy the JAR with the old name (my-proejct-0.0.1-SNAPSHOT.jar) on my maven distribution repository.
How can I solve this?