I'm noticing that in Maven the group id's are not getting fleshed out for our projects. For instance in Math.
<project>
<extend>../../jakarta-commons/project.xml</extend>
<name>Math</name>
<id>commons-math</id>
<currentVersion>0.1-dev</currentVersion>
<inceptionYear>2003</inceptionYear>
<logo>/images/math.gif</logo>
<shortDescription>
Jakarta Commons Math
</shortDescription>
this results for one, in projects having the same group-id and id in the Maven repository, for instance:
http://jakarta.apache.org/commons/math/dependencies.html
and in the maven repository for example:
http://www.ibiblio.org/maven/commons-httpclient/
Shouldn't we really start setting our group id's?
http://maven.apache.org/reference/user-guide.html#Naming%20Conventions
<id>foo</id> <name>The Grand Master Foo</name> <groupId>org.foo.bar</groupId>
for instance in math:
> <project> > <extend>../../jakarta-commons/project.xml</extend> > <name>Math</name> > <id>commons-math</id> > <groupId>org.apache.commons.math</groupId> > <currentVersion>0.1-dev</currentVersion> > <inceptionYear>2003</inceptionYear> > <logo>/images/math.gif</logo> > <shortDescription> > Jakarta Commons Math > </shortDescription>
This would end up in the repository under:
http://www.ibibilio.org/maven/<org.apache.commons.math>/<type>/commons-math-<version>.<ext>
Eventualy aven is going to process these group-id's into directory structures:
http://www.ibibilio.org/maven/org/apache/commons/math/<type>/commons-math-<version>.<ext>
which would keep all the commons code grouped and well organized once this occurs.
-Mark
-- Mark Diggory Software Developer Harvard MIT Data Center http://www.hmdc.harvard.edu
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
