JBoss module/jar naming

[dimitris]

Nothing too important but we don't have a consistent naming convention for jboss modules. Going forward, can we come up with something consistent:

In the legacy repository some modules appear like jboss/xxx others jboss/jboss-xxx, yet others jboss/jbossxxx:

[dimitris]

Sure enough, I forgot to quote:

 <componentref name="jboss/aop" version="2.0.0.CR1"/>
 <componentref name="jboss/cache" version="2.1.0.CR2"/>
 <componentref name="jboss/common-core" version="2.2.3.GA"/>
 <componentref name="jboss/common-logging-jdk" version="2.0.2.GA"/>
 <componentref name="jboss/common-logging-log4j" version="2.0.2.GA"/>
 <componentref name="jboss/common-logging-spi" version="2.0.2.GA"/>
 <componentref name="jboss/integration" version="5.0.0.Beta4"/>
 <componentref name="jboss/jaxr" version="1.2.0.GA"/>
 <componentref name="jboss/jboss-ejb3-cache" version="0.11.1"/>
 <componentref name="jboss/jboss-ejb3-ext-api" version="0.1.2.Beta1"/>
 <componentref name="jboss/jboss-ejb3-impl" version="0.1.2.Beta1"/>
 <componentref name="jboss/jboss-ha-client" version="1.0.0.BETA1"/>
 <componentref name="jboss/jboss-ha-server-api" version="1.0.0.BETA2-SNAPSHOT"/>
 <componentref name="jboss/jboss-jaspi-api" version="1.0-BETA1"/>
 <componentref name="jboss/jboss-javaee" version="5.0.0.Beta3Update1"/>
 <componentref name="jboss/jboss-security-spi" version="2.0.2.Beta3"/>
 <componentref name="jboss/jbosssx" version="2.0.2.Beta3"/>
 <componentref name="jboss/jbosssx-client" version="2.0.2.Beta3"/>
 <componentref name="jboss/jbossts" version="4.3.0.BETA2"/>
 <componentref name="jboss/jboss-vfs" version="2.0.0.Beta6"/>
 <componentref name="jboss/jbossws-native50" version="2.0.2.GA"/>
 <componentref name="jboss/jbossxb" version="2.0.0.CR5"/>
 <componentref name="jboss/jms-integration-tests" version="1.0.1.GA"/>
 <componentref name="jboss/messaging" version="1.4.0.SP3"/>
 <componentref name="jboss/metadata" version="1.0.0.Beta5"/>
 <componentref name="jboss/microcontainer" version="snapshot"/>
 <componentref name="jboss/profiler/jvmti" version="1.0.0.CR5"/>
 <componentref name="jboss/remoting" version="2.2.2.SP3-brew"/>
 <componentref name="jboss/serialization" version="1.0.3.GA"/>
 <componentref name="jboss/test" version="1.0.4.GA"/>
 <componentref name="jboss/web" version="2.1.0.CR11"/>

[starksm64]

Regarding the jboss repo location, I just forgot that the names were not consistent with the mvn artifact name. Where it exists, it should be consistent.

Another thing to look at is using only the mvn repo and integrating into non-mvn builds using the various ant to mvn integration tasks.