Hey all,
A recent discussion on one of the github PR's led to a discussion on
SNAPSHOT resolution, which is a long standing issue in maven range
support with several long standing open tickets lingering.
A thought I just had, which relates to some things I've been playing
with in my C.I. builds, could quite simply resolve this. Maybe....
I know a few people who say "they just don't allow/use SNAPSHOTs" but
whenever you do an `mvm install` you end up with a -SNAPSHOT in your
~/.m2/repository - and that then affects resolution.
My thought was.... why is the local _repository_ treated differently to
normal repositories - in that it's as tho
`<snapshots><enabled>true</enabled></snapshots>` is defined for them -
and maybe it is? Why not simply.... _disable_ that.
But further than that, what if maven tracked TWO local repositories:
~/.m2/repository
~/.m2/snapshots
Much like `distributionManagement ` has two a `repository` and
`snapshotRepository` section, what if we have an
`installationManagement` section ( probably limited only to
`settings.xml` for install wide settings? ) that did the same, but for
the local repository? -SNAPSHOTs installed via `mvn install` or
downloaded via dependencies would go in here.
This way - there's a clear separation of snapshots and releases, if you
don't want snapshot resolution - disable that local repository....
Thoughts?
Mark
