title: Can Maven model an "Always use the latest" release system?
body: <p>I would like to implement a release system similar to the one used at a large PNW company at which I worked recently.  I would like to know if I can model it with Maven (to which I am relatively new).</p>
  
  <p>I have applications A1, A2, ..., An.  They depend on library L.  I would like to designate the next release of L to be version 2.0.  I would like A1 - An to declare dependency on L v2.0.</p>
  
  <p>I would then like to release successive L artifacts, preferably named something like L-[timestamp]-[git-hash] (so that, given an artifact, I can identify the source that created it) as L v2.0.  Any subsequent rebuilds of any of A1 - An would build against that newly-released version.</p>
  
  <p>Can I do this with Maven?</p>