Snapshot Versions Vs. Incremental Versions

scmuser created the topic: SNAPSHOT versions Vs. incremental versions
SNAPSHOT versions Vs. incremental versions

Hi All,

I am in a process of pushing Maven in my organization and I have a methodology question.
Up until now (before Maven), in most R&D teams, the development was broken into builds. If, for example we have a module called “my-module” with version 4.7.1.0, each build produced a jar will the following method:
My-module-4.7.1.0-01 (for build number 1)
My-module-4.7.1.0-02 (for build number 2)
And so on…

Now, when the module is built with Maven, each time the team deploy the module to Maven repository (release type), there is a new release version.
I think, the better way is to use SNAPSHOT version during development, so that all artifacts are under the same version umbrella. The problem is that the teams want to have a significant artifact for each build, something that says: this artifact is of build number 6…

1) Do you agree with me that the SNAPSHOT way is better?

2) Can you give your reasons of why this is better?

Rajesh Kumar

I’m Rajesh Kumar, a DevOps, SRE, DevSecOps, Cloud, and Platform Engineering expert passionate about sharing practical knowledge, real-world experiences, and industry best practices. I have worked at Cotocus and regularly write about technology, travel, investing, health, product reviews, and digital marketing through my various platforms.

I publish technical articles at DevOps School, travel stories at Holiday Landmark, stock market insights at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at TrueReviewNow, and SEO and digital marketing strategies at Wizbrand.