Re: [jboss-dev] Usage of consistent groupIds/artifactIds

So just after the discussion about having consistent groupIds/artifactIds, jboss web 2.1.0.GA was added in the maven repo. Shouldn't that go to: maven2/org/jboss/web instead??? -------- Original Message -------- Subject: [jboss-cvs] Repository SVN: r2787 - in maven2/jboss/web: el-api and 9 other directories. Date: Mon, 17 Mar 2008 11:57:49 -0400 From: jboss-cvs-commits(a)lists.jboss.org Reply-To: jboss-cvs-commits(a)lists.jboss.org To: jboss-cvs-commits(a)lists.jboss.org Author: pgier Date: 2008-03-17 11:57:49 -0400 (Mon, 17 Mar 2008) New Revision: 2787 Added: maven2/jboss/web/el-api/ maven2/jboss/web/el-api/2.1.0.GA/ maven2/jboss/web/el-api/2.1.0.GA/el-api-2.1.0.GA.jar maven2/jboss/web/el-api/2.1.0.GA/el-api-2.1.0.GA.jar.md5 maven2/jboss/web/el-api/2.1.0.GA/el-api-2.1.0.GA.jar.sha1 maven2/jboss/web/el-api/2.1.0.GA/el-api-2.1.0.GA.pom maven2/jboss/web/el-api/2.1.0.GA/el-api-2.1.0.GA.pom.md5 maven2/jboss/web/el-api/2.1.0.GA/el-api-2.1.0.GA.pom.sha1 maven2/jboss/web/el-api/maven-metadata.xml maven2/jboss/web/el-api/maven-metadata.xml.md5 maven2/jboss/web/el-api/maven-metadata.xml.sha1 maven2/jboss/web/jasper-jdt/ maven2/jboss/web/jasper-jdt/2.1.0.GA/ maven2/jboss/web/jasper-jdt/2.1.0.GA/jasper-jdt-2.1.0.GA.jar maven2/jboss/web/jasper-jdt/2.1.0.GA/jasper-jdt-2.1.0.GA.jar.md5 maven2/jboss/web/jasper-jdt/2.1.0.GA/jasper-jdt-2.1.0.GA.jar.sha1 maven2/jboss/web/jasper-jdt/2.1.0.GA/jasper-jdt-2.1.0.GA.pom maven2/jboss/web/jasper-jdt/2.1.0.GA/jasper-jdt-2.1.0.GA.pom.md5 maven2/jboss/web/jasper-jdt/2.1.0.GA/jasper-jdt-2.1.0.GA.pom.sha1 maven2/jboss/web/jasper-jdt/maven-metadata.xml maven2/jboss/web/jasper-jdt/maven-metadata.xml.md5 maven2/jboss/web/jasper-jdt/maven-metadata.xml.sha1 maven2/jboss/web/jbossweb/2.1.0.GA/ maven2/jboss/web/jbossweb/2.1.0.GA/jbossweb-2.1.0.GA-sources.jar maven2/jboss/web/jbossweb/2.1.0.GA/jbossweb-2.1.0.GA-sources.jar.md5 maven2/jboss/web/jbossweb/2.1.0.GA/jbossweb-2.1.0.GA-sources.jar.sha1 maven2/jboss/web/jbossweb/2.1.0.GA/jbossweb-2.1.0.GA.jar maven2/jboss/web/jbossweb/2.1.0.GA/jbossweb-2.1.0.GA.jar.md5 maven2/jboss/web/jbossweb/2.1.0.GA/jbossweb-2.1.0.GA.jar.sha1 maven2/jboss/web/jbossweb/2.1.0.GA/jbossweb-2.1.0.GA.pom maven2/jboss/web/jbossweb/2.1.0.GA/jbossweb-2.1.0.GA.pom.md5 maven2/jboss/web/jbossweb/2.1.0.GA/jbossweb-2.1.0.GA.pom.sha1 maven2/jboss/web/jsp-api/ maven2/jboss/web/jsp-api/2.1.0.GA/ maven2/jboss/web/jsp-api/2.1.0.GA/jsp-api-2.1.0.GA.jar maven2/jboss/web/jsp-api/2.1.0.GA/jsp-api-2.1.0.GA.jar.md5 maven2/jboss/web/jsp-api/2.1.0.GA/jsp-api-2.1.0.GA.jar.sha1 maven2/jboss/web/jsp-api/2.1.0.GA/jsp-api-2.1.0.GA.pom maven2/jboss/web/jsp-api/2.1.0.GA/jsp-api-2.1.0.GA.pom.md5 maven2/jboss/web/jsp-api/2.1.0.GA/jsp-api-2.1.0.GA.pom.sha1 maven2/jboss/web/jsp-api/maven-metadata.xml maven2/jboss/web/jsp-api/maven-metadata.xml.md5 maven2/jboss/web/jsp-api/maven-metadata.xml.sha1 maven2/jboss/web/servlet-api/ maven2/jboss/web/servlet-api/2.1.0.GA/ maven2/jboss/web/servlet-api/2.1.0.GA/servlet-api-2.1.0.GA.jar maven2/jboss/web/servlet-api/2.1.0.GA/servlet-api-2.1.0.GA.jar.md5 maven2/jboss/web/servlet-api/2.1.0.GA/servlet-api-2.1.0.GA.jar.sha1 maven2/jboss/web/servlet-api/2.1.0.GA/servlet-api-2.1.0.GA.pom maven2/jboss/web/servlet-api/2.1.0.GA/servlet-api-2.1.0.GA.pom.md5 maven2/jboss/web/servlet-api/2.1.0.GA/servlet-api-2.1.0.GA.pom.sha1 maven2/jboss/web/servlet-api/maven-metadata.xml maven2/jboss/web/servlet-api/maven-metadata.xml.md5 maven2/jboss/web/servlet-api/maven-metadata.xml.sha1 Removed: maven2/jboss/web/2.0.1.CR7/ maven2/jboss/web/2.1.0.CR4/ maven2/jboss/web/maven-metadata.xml maven2/jboss/web/maven-metadata.xml.md5 maven2/jboss/web/maven-metadata.xml.sha1 Modified: maven2/jboss/web/jbossweb/maven-metadata.xml maven2/jboss/web/jbossweb/maven-metadata.xml.md5 maven2/jboss/web/jbossweb/maven-metadata.xml.sha1 Log: [JBBUILD-459] Adding jboss web 2.1.0.GA artifacts to repository. Removing some files that were not deployed to the correct location. Pete Muir wrote: > On 14 Mar 2008, at 12:41, Dimitris Andreadis wrote: > >> Going forward, can we agree on a common set of guidelines what goes >> where? Or else, define consistent groupIds not only for jboss >> projects but for the thirdparty ones, too? Aren't there any maven >> best practises? > > Maven2 standarises on > > <groupId>org.jboss.seam</groupId> > <artifactId>jboss-seam-mail</artifactId> > <version>2.0.1.GA</version> > <packaging>jar</packaging> > <scope>runtime</scope> > > with the common shorthand of: > org.jboss.seam:jboss-seam-mail:jar:2.0.1.GA:runtime > > This produces a jar called jboss-seam-mail.jar. > >> Can we remove legacy maven stuff that is probably not in use yet? >> (that could be tricky) > > Be careful, as other projects (e.g. Seam ;-) are using the repo too. > > -- > Pete Muir > http://www.seamframework.org > http://in.relation.to/Bloggers/Pete > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development