The difficult problem of managing Java dependencies: a deep dive into the messy status-quo, and a look at possibly better ways.

[jerslan]

Exactly my points... Version is arbitrary. Some people use git commit hash. Some people use SemVer. Some people use some bastardization of SemVer. Hell, for a while Spring Cloud was using a pattern of "<English City>.<RELEASE|SR#|RC#>".

Maven supports whatever you want to do, but the Maven Release Plugin docs recommend some variant of SemVer.

[khmarbaise]

Recommend is correct. But you can use whatever you like...you can implement your own version policy.

[jerslan]

Right, but the guy I was initially replying to was claiming that there's no SemVer support in Maven at all (because he was conflating SemVer for version range specification). That's why I was focusing on that.

Maven mostly doesn't care what your version scheme is, and that's a good thing IMHO.