On 11/15/06, Gilles Scokart <[EMAIL PROTECTED]> wrote:
It would be a good thing to add the focus on java project into the description of ivy (http://incubator.apache.org/projects/ivy.html).
Well, I don't know how important it is. Ivy has been designed to address dependency management, but is more focused on Java dependency management, because it's a java tool and because of its defaults values (jar for artifacts types for instance). But it isn't only java focused. On the other hand, I don't think it can compete with tools like ruby gems or perl CPAN, because they are tools dedicated to other languages, and will always be better for those languages needs. I don't say I don't want to say that Ivy is java focused, I don't mind, I don't think I'll ever use it for something else. But if a user community appear who want to use it to deal with another language dependency management, and if they submit patches to better support it, I think this could be easily accepted as soon as it doesn't alter the core philosophy. Xavier Gilles
> -----Original Message----- > From: Xavier Hanin [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 15, 2006 12:38 PM > To: [email protected] > Subject: Re: Dependency standards > > > I don't think it means much for Ivy, because there is no real > standard in the area of Java dependency management. > > On non java technologies (like apt and rpm) you have also > .NET assembly, perl CPAN, ruby gem, and certainly many else. > But I don't know if we have to quote such technologies, since > they are not easily usable with Java, and Ivy has a focus on > java dependency management. >
