www-repository mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From robert burrell donkin <rdon...@apache.org>
Subject Re: Maven repository policies
Date Wed, 27 Jul 2005 21:11:15 GMT
On Tue, 2005-07-26 at 07:12 -0700, Phil Steitz wrote:
> Brett Porter wrote:

<snip>

> > 3) require long groupId's. Currently the top level directory is polluted
> > with a lot of different project names. I would like projects to use
> > org.apache.project.subproject as the groupId so that it uses the
> > directory structure /org/apache/project/subproject keeping individual
> > directories with less files in them. The longest I can think of would be
> > org.apache.jakarta.commons.collections. This should also be done for any
> > future Maven 1 based releases (it works identically, but retains a
> > shallow structure in the Maven 1 layout).
> 
> I don't know enough about maven repository management to understand 
> fully the implications of this, but it seems to me that leaving 
> "jakarta" out of the name adds flexibility with no loss of specificity. 
>   So, if one day commons is a TLP, we do not have to rename.  It seems 
> more natural to me to mirror the package names, but again I don't claim 
> to understand all of the issues here.

this is a good point: organisations change but code continues. 

why not just use package names?

- robert

Mime
View raw message