On 23/11/2013 7:31 AM, Viktor Sadovnikov wrote:
Thank you very much for your responses!! It's very supportive!!
@Ziga, your suggestion to limit access to snapshot repository for CI
servers only is a very, very interesting one. I'll give it a thought/try.
However dependency on a snapshot of some
Thank you very much for your responses!! It's very supportive!!
@Ziga, your suggestion to limit access to snapshot repository for CI
servers only is a very, very interesting one. I'll give it a thought/try.
However dependency on a snapshot of something, which does not get built
together with your
Baptiste, you got it.
Jeff
On Sat, Nov 23, 2013 at 10:50 AM, Baptiste Mathus wrote:
> I guess Jeff is only speaking about version ranges, not snapshots.
>
> If so, I'm +1 with Jeff. I don't think version ranges should ever be used.
>
> Cheers
> Le 23 nov. 2013 00:18, "Ziga GREGORIC" a écrit :
I guess Jeff is only speaking about version ranges, not snapshots.
If so, I'm +1 with Jeff. I don't think version ranges should ever be used.
Cheers
Le 23 nov. 2013 00:18, "Ziga GREGORIC" a écrit :
> Jeff, maybe I'm missing the point, but to have the possibility to define a
> SNAPSHOT version o
Jeff, maybe I'm missing the point, but to have the possibility to define a
SNAPSHOT version of a dependency is the beauty of maven IMHO.
Having said that, I would not feel safe in a large project where lots of
dependencies are SNAPSHOT dependencies. But when you have a continuous
integration serve
Having a build using non identified dependencies (LATEST,...) is a VERY bad
practice: the build is not reproducible and your team will not have
attentions on dependencies versions.
A non existing case for me.
Jeff
On Fri, Nov 22, 2013 at 5:11 PM, Viktor Sadovnikov wrote:
> Hello,
>
> Here is an
Wasn't it just the mvn -U to force updating snapshots you were looking for?
Cheers
2013/11/22 Russell Gold
> It’s also an attempt to create a modular system, in hopes of minimizing
> codebase size and providing custom functionality. It’s thus closely related
> to a lot of the modularity ideas
It’s also an attempt to create a modular system, in hopes of minimizing
codebase size and providing custom functionality. It’s thus closely related to
a lot of the modularity ideas that have come and gone over time, without the
judgment of what is properly a “module.” I’ve seen multi-hundred mod
Looks like a kludge to get around a poor SOA architecture with too many
inter-module dependencies and an unwillingness to build mock objects for
testing.
In our house, SNAPSHOTS posted to Nexus come with a warranty that they
meet a subset of the spec that is known.
If someone doesn't like that
