It is clear version ranges are used by some people and they do find them
useful including me. You cannot predict how and in what circumstances
specific features of maven will be used by the many people out there,
good or bad in your opinion.
I still would prefer making version range calculations pluggable where a
default is supplied (the current). I can then create my own plugin which
overrides the default and specify it my POM. For example I would
probably use semantic versioning on artifacts in specific groups which I
specify and use specific versions for others. Who knows? The fact of the
matter is I can do what I like and the build will be repeatable (in
terms of the version range calculation).
Currently when we release an artifact or product we have created a
release plugin which creates an effective POM listing all versions used,
including the transistive ones. Hence our release builds are repeatable.
We can go back in time, branch and fix.
The biggest pain we have is the speed of the dependency calculation when
developing. I'm sure this can be optimized.
On 01/10/2012 07:22, Hervé BOUTEMY wrote:
Le lundi 1 octobre 2012 02:31:44 Jesse Long a écrit :
I have created a ticket - http://jira.codehaus.org/browse/MNG-5353
thank you
I changed it from "Bug" to "Wish": no, nobody ever asked for such a behaviour,
it's really a new idea AFAIK
which BTW seems a good enhancement IMHO
now we need to check with people using ranges that it is ok for them: if
anybody can think of a problem, please share
Regards,
Hervé
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
