> -----Original Message----- > From: Xavier Hanin [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 15, 2006 4:33 PM > To: [email protected] > Subject: Re: Dependency standards > > 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 >
Thanks for the clarification. By the way, there is an other point to clarify concerning the scope of ivy. It is how far ivy goes (or want to go) in term of repository management. There is already some important steps that ivy cover : how to access a repository and how to fill a repository, how to search artefact in a repository (limited to searching for last integration, last release, etc), replicating/transforming repositories... Etc. What is the intention there? Where will ivy stop? (expl: more advanced search, cleaning repositories)
