On Wed, Apr 16, 2008 at 8:56 AM, Gilles Scokart <[EMAIL PROTECTED]> wrote:
> On 16/04/2008, Xavier Hanin <[EMAIL PROTECTED]> wrote: > > On Wed, Apr 16, 2008 at 8:37 AM, Gilles Scokart <[EMAIL PROTECTED]> > wrote: > > > > > Maven has naming conventions [1], [2]. > > > > > > The problem is that those conventions apeared with maven 2. maven 1 > > > didn't had this and the maven repository actully contains an export > of > > > the maven 1 repository. That's why the naming convention didn't > > > seemed to be always followed. > > > > > > Note however, that they give advices to fix that [3]. > > > > > > The problem is that the repository is cluttered with old naming > conventions, > > which make it sometimes difficult for users to find their way out: > > http://javarepo.xoocode.org/search?q=%23hibernate%3B > > http://javarepo.xoocode.org/search?q=%23commons-email%3B > > http://javarepo.xoocode.org/search?q=%23commons-transaction%3B > > http://javarepo.xoocode.org/search?q=%23commons-collections%3B > > > > I agree, but in some case there are hints that one has replaced the other. > If you look for instance at the latest version of > commons-email:commons-email (version 1.1), it say that it has been > relocated. That may be an information that could be exploited. Indeed. That could be exploited by a tool to create a new cleaner repository like Ivy roundup. OTOH most end users don't check the metadata before adding their dependency to their module, and thus are now aware of this relocation information. Xavier > > > -- > Gilles Scokart > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/ http://www.xoocode.org/
