[jboss-dev-forums] [Design of JBoss Build System] - JBoss Build Status Meeting Notes Feb 1, 2007

[pgier]

Remaining tasks to complete before micro container mavenization is complete
Add a snapshot version of JBossTest to the maven2 repository.  (JBoss Test can also be mavenized soon).
JBossRetro will be called by the antrun plugin until a maven2 plugin version can be created.

POM structure
 There should be a single parent pom that all JBoss proejcts will inherit default configuration from. 
Microcontainer and JBoss common will initially each use the build/pom.xml as the parent pom.  Later will be re factored to share a single parent. 

Project artifact naming convention
Project groupId will be "jboss" for all projects.  
artifactId will be the name of the project or subproject

Synchronization of jboss maven repository with main maven repo.
All JBoss project builds should be dependent only on the JBoss repository.
Uploading JBoss artifacts to main maven repository is low priority and can be manually done as needed.

Cleanup of Maven2 repository
Paul will begin removing old stuff from the jboss repository.  Maybe we can create something automated to find artifacts that are not depended upon.
We will look into using ant tasks to pull artifacts from the maven2 repository instead of the current one for existing builds.  This would allow us to merge the two repositories before fully converting to maven.

Subversion Migration
Will work with IT to migrate remaining projects from CVS to subversion.  Starting with JBoss Serialization and then Seam, JBoss Remoting, and maybe JBossRetro and the maven repository.

Other notes
We will have a bi-weekly meeting to provide an update of the status of the build system.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010067#4010067

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010067