One aspect of using ivy that I've noticed is the larger the deployment, and
the greater the integration into the product lines, the more a kind of
emergent behaviour emerges. Sometimes the source of the problem (which
usually manifests itself as being unable to locate an artifact that is quite
Kirby Files wrote on 11/09/2009 14:45:09:
> Sebastian Krysmanski wrote on 09/11/2009 04:16 AM:
> > So the tradeoff is:
> >
> > * without Ivy: slower initial checkout; but easier to use (works out
of the
> > box) and easier to manage (simply place every necessary library in the
VCS
> > repository
Sebastian Krysmanski wrote on 09/11/2009 04:16 AM:
So the tradeoff is:
* without Ivy: slower initial checkout; but easier to use (works out of the
box) and easier to manage (simply place every necessary library in the VCS
repository)
* with Ivy: faster initial checkout; but not as easy to use (n
> > However I see a major disadvantage over dependencies in a VCS
repository: If
> > a project is dormant for a longer period of time an artifact (i.e. a
> > library) may longer be available (in a certain, required version or the
> > repository may not exist anymore).
> If you download all your de
Sebastian,
recently someone recommended Ivy to me because he saw that we were hosting
our project dependencies in our Subversion repository.
When I see axis.jar in a VCS system, I always ask the question: "do
you know which version it is?". If you're serious about managing the
3rd party l
Thanks for the insight. This was really helpful. In your case I can see why
you want to use Ivy. Fortunately(?) we don't have such requirements in our
project. So, I think we'll stick with placing our libraries in our VCS.
Regards
Sebastian
-Ursprüngliche Nachricht-
Von: Shawn Castrianni
I use IVY heavily for my entire corporate R&D group. I designed all the ANT
scripts for the entire company and would not think of going back to checking in
dependencies into a VCS. My reaction to this summary is that it is mostly
true, but it depends on what your environment and requirements a
Hi,
just my 2 cents: we use both, a local VCS and ivy in combination.
The VCS we use to "control" the appearing (and disappearing) of libraries. All
developers sync the libs to their local disk/development environment with VCS
mechanisms.
The ivy is a great help for us for dependencies res
Hi all,
thanks for all the answers. To just summarize for me what has been said
(correct me, if I'm wrong):
* This big(gest) (and only?) disadvantage of storing the dependencies in a
VCS is the time needed to checkout a project. It's faster when you don't
have to check out all the dependencies. T
