I think it can be in the same vein as the no versions for plugins. Not
a very good idea and potentially harmful.
We put it in, deprecate it over 3.0 and it becomes taboo in 3.1. If
it's a bad practice in the majority of cases then we eliminate it.
Over the life of 3.0 to 3.1 should be long enough. We can also start
deprecating things like this in the 2.x line.
On 2009-09-04, at 4:49 PM, Brian Fox wrote:
I saw this on Benjamin's compat page yesterday and thought I'd throw
it up for discussion:
Non-unique Snapshot Deployments
The setting <uniqueVersion>false</uniqueVersion> for a distribution
repository has no effect in version 3.x, snapshot artifacts will
always be deployed using a timestamped version.
I personally am not a fan of this feature as I've seen it cause more
problems than it solves. It also harkens back to a time when
Repository Managers didn't exist and seems like a work around to
cleaning up old snapshots. So my life would be easier if this didn't
exist.
That said, I know of at least one instance where this is required
(will send a separate thread about that because it's a flaw in Maven
that should be addressed separately).
With the focus on 3.0 being a drop in for M2, this clearly would cause
some heartache for users. Does anyone feel strongly enough that this
should go back? (and is willing to write the new code for it?)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/SonatypeNexus
http://twitter.com/SonatypeM2E
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
