Mark R. Diggory wrote:
No, you missunderstood me, we're not breaking up the repository, its still all one, just organizing it better for management purposes, the directory structure is not different virtual machines.
maven.ibibilio.org/apache/<project> maven.ibibilio.org/codehaus/<project>
same thing as
www.ibibilio.org/maven/apache/<project> www.ibibilio.org/maven/codehaus/<project>
Ultimately the issue here is in organization/group/artifact id's being more hierarchical, not separating out into separate repositories.
I undestand what you're saying, but from the point of view of the maven client these are two separate remote repos.
I saw the big advantage of ibiblio as being a source-agnostic repository of projects artifacts with a flat structure. Else you would need a "all others" organization level for projects that don't fit into any other category.
I guess what I'm asking is if the benefits of the organizational structure are outweighted by the loss of simplicity and generality.
We are discussing the future Maven2 client/repository here, not the current client. In the future Repository URI syntax there is a positional space in the uri for "organization" so that the content can be organized by the following
<repository>/<organization>/<project>/<type>/<artifact>
Sorry if this caused confusion, Mark
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
