ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kirby Files <>
Subject RE: Question about documentation
Date Tue, 05 Oct 2010 12:30:15 GMT
Sorry, David, I cannot help provide a link to different documentation. In regards to understanding
Ivy better, one thing that I'd recommend is reading everything you can about the dependency
conf attribute and defaultConfMapping. I didn't truly understand what I was doing with Ivy
until I had a good grasp on how Ivy configurations worked for recursive dependencies.

If you want specific help rather than just discussing your frustration, please provide ivy.settings,
ivy.xml files, ant fragments, and the issues you are having, and usually many people on this
list are happy to help.

Kirby Files
Software Architect
Masergy Communications

From: David Sills []
Sent: Tuesday, October 05, 2010 8:11 AM
Subject: Question about documentation

To whom it may concern:

Help! :)

I am a Java developer with 10 years experience, a masters degree, an IQ
above 160, and an excellent work ethic. I have spent 5 days trying to
figure out how to add Ivy to my current project. I do not have another 5
days - that's just not practical at my job.

I have read document after document, including the complete tutorial and
reference documentation. I have read the section in Ant in Action,
several apparently useful resources and blogs on the web.

And still I have been completely unable to make even the simplest Ivy
configuration work for what should be an easy project. (One JAR file,
two JAR file dependencies.)

If anyone is actually interested having documentation written (or maybe
a book, who knows) that can be read by someone who doesn't understand a
thing about Ivy, I would be willing to contribute to or even author
that. But first, I have to understand what's going on myself.

All the examples I see are either way too simple or way too specific to
a particular project. The reference documentation doesn't really explain
what each attribute does in each file - it merely adds an English
description (which is sometimes self-referential).

This is what I see so often in open-source projects: the documentation
is read by people who don't need to read it to understand things - they
already understand them. They only need to be reminded of things they
already know. And it doesn't occur to them (understandably, to be sure)
that someone who doesn't understand what they do might be confused by a
lot of extremely abstract terminology without really practical examples.

I'm obviously not the first person to have this problem. A lot of people
I have read love Ivy but bewail the state of its documentation. I'd be
happy to help, but can someone first point me in the direction of a
step-by-step description of using Ivy? And I don't mean the tutorial,
which is fine but assumes a lot of things it doesn't specify.

If Ivy's not for me, then who is it for? I'm an expert in using Ant and
really don't like Maven's inflexibility. Ivy sounded like the perfect
solution. But even with the best will in the world, I couldn't get

Sorry for the rant. Somebody please point me to the blog where they
describe this "for dummies" (I'm not above this at all) and I'll just go
and make it work. Thanks!

David Sills

View raw message