On Wed, Apr 16, 2008 at 1:45 AM, 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 > By the way, I've been thinking about this problem as well. Since Ivy RoundUp builds its repository using ant, it would be easy to add "meta-data meta-data" that would handle things like backward-compatible aliases for organisation names. E.g., if a Hibernate is officially known under org="org.hibernate" but unofficially with org="hibernate" and org="net.sf.hibernate", then we could add a file in src/modules/org.hibernate/aliases.xml: <aliases> <alias org="hibernate"/> <alias org="net.sf.hibernate"/> </aliases> Then the build would automatically create copies of the module under both locations in the repo. Actually, an even simpler way would be with a symlink checked into SVN... You could do similar things with the module name as well of course. In any case, the larger point is that the RoundUp project could provide ways to help these kinds of issues. -Archie -- Archie L. Cobbs
