Hello.
This is something that has been troubling me for some time now.
When we perform release staging, the artifact version in the tag pom is the
result of removing the "-SNAPSHOT" suffix to the original version.
For example, 1.2.3-SNAPSHOT will be converted to 1.2.3 in the tag pom. This
is the way the Maven release plugin and Artifactory plugin behave by
default.
This may be good in many cases but in others, not so much.
For example: suppose that:
- Artifact A depends on B 1.0-SNAPSHOT
- Both artifacts are developed by different teams
- Both A and B are developing at the same time
- Every now and then, B does a staging to test in QA.
When B performs release staging, its version will be incremented each time:
1.1-SNAPSHOT, 1.2-SNAPSHOT, and so on.
As a result, A loses sync with B because it will be still be pointing to B
1.0-SNAPSHOT and it will be a bit of a pain for A to update their POM every
time B stages.
So, in our dev cycle, when releasing I prefer that my dev POM is not
changed (i.e, Next development version = 1.0-SNAPSHOT)
But for this to make sense, the tag needs to add an incremental number to
the POM, such as the Jenkins build number. Example: 1.0-1, 1.0-2, 1.0-3,
etc. (they don't need to sequential if we use the Jenkins build number).
Wouldn't it be useful to add the possibility of specifying the tag version
and maybe provide a variable to referentiate the Jenkins build number?
Cheers.
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
