Maven best practices: including timestamps for snapshot releases or not?

Question

I recently added Maven snapshot build capability to a project, configured to use unique timestamp version on deployed artifact. But there is some confusion regarding whether this is the right thing to do (snapshots in question are deployed to one of public repos, not just within an entity like company): some say it causes problems when trying to use snapshots.

So: given how much of Maven is convention based, and following perceived best practices, I am hoping there are some guidelines as to which option to choose.

(NOTE: I slightly edited the title -- I am specifically interesting in benefits (or lack thereof) of including unique timestamp, via deploy option, for public snapshot versions; not so much whether to make use of timestamps if they are included, although that is obviously somewhat related question)

Answer 1

The whole point of a snapshot is to let someone use the latest version of the code. Why would you want to use a snapshot five versions back?

With that in mind, what do timestamps in the artifact name buy you?

I've been using Maven for about 5 years now. I've never seen a snapshot jar with a timestamp in the name.

Answer 2

As a rule you should always build against the -SNAPSHOT dependency. However, you should avoid releasing your product if it includes -SNAPSHOT dependencies. If you use the Maven Release Plug-in to automate your release it will check to make sure you are not using release plug-ins or dependencies.

But that is not always possible. In cases where I need to release something based on a snapshot build that is when I use the explicit timestamp/build number rather than the -SNAPSHOT version naming scheme.

You can automate this using the Versions Maven Plugin. It provides goals to lock and unlock snapshot versions in your POM.