-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
When using the maven release plugin, it updates the <scm><tag>...</tag></scm> value to match the scm tag for that release.
So for example:
<project>
...
<version>4.2-SNAPSHOT</version>
<scm>
<developerConnection>scm:git:https://github.com/MY_TEAM/my_project.git</developerConnection>
<tag>HEAD</tag>
</scm>
...
</project>
is changed to
<project>
...
<version>4.2</version>
<scm>
<developerConnection>scm:git:https://github.com/MY_TEAM/my_project.git</developerConnection>
<tag>my_project_4.2</tag>
</scm>
...
</project>
for the release and then to
<project>
...
<version>4.3-SNAPSHOT</version>
<scm>
<developerConnection>scm:git:https://github.com/MY_TEAM/my_project.git</developerConnection>
<tag>HEAD</tag>
</scm>
...
</project>
for the next snapshot version.
This is really handy for being able to instantly track a jar (with pom file) back to the source it was released from.
Improvement: Add this behavior to the Jenkins Artifactory plugin.