On Fri, Dec 21, 2012 at 5:39 AM, Christian Trutz
wrote:
> Hi Tony, hi Ceki,
>
> I am a big fan of standard things (convention-over-configuration) and you
> convinced me to change my opinion.
> Because of easiness of "versions:set" and advantages of SNAPSHOT, I think
> now, it is better to use the
Hi Tony, hi Ceki,
I am a big fan of standard things (convention-over-configuration) and you
convinced me to change my opinion.
Because of easiness of "versions:set" and advantages of SNAPSHOT, I think
now, it is better to use the "standard workflow"
with SNAPSHOT versions during developing.
@Tony
Hi Christian,
That's ok with me, but I would like to explain why I personally prefer to
use the SNAPSHOT qualifier.
Maven has special handling [1] for SNAPSHOT versions (specifically with
this suffix) that allows users to have projects that automatically download
bleeding-edge builds from the sna
While we wait for Tony's comments, I'd like to chime in. I sometimes
work on projects with a version lacking the "SNAPSHOT" suffix, in
particular when a release is imminent. So it's definitely possible to
work as you are suggesting. It would save a version change operation
between releases but
