[Jboss-dev-forums] [Design of JBoss Build System] - Re: JBoss Third Party Build

[<sco...@jb...>]

1) This is because there is a notion of a component and it can be either a source or binary module? The hibernate integration module can be changed in the current jboss-4.0.x definition:


  | jboss-4.0.x        -d jboss-4.0 \
  |                         &_jboss_aop \
  | ...
  |                         -d har  hibernate \
  | ...
  | 

The build.xml modules reference to hibernate would have to be changed locally to do the build.

2) There certainly is tons of garbarge in there. The thirdparty build should be created by only referencing the direct dependencies of the toplevel components. Build the thirdparty strucuture and try the build and add thirdparty componentrefs as needed until it builds.

3) As Ryan said, drop the double name usage as its a cvs hack issue that we should not propagate.

4) The only place the new thirdparty lib names should be showing up at is in the libraries.ent definitions. Nearly all build files in the modules should simply be referencing the *.classpath from librariens.ent. The only problem will be that there will not be an aggregate classpath like apache.commons.classpath. You could deal with this by adding a notion of being able to merge multiple component paths to the libraries.ent generation:


  |   <path id="apache.commons.classpath">
  |     <componentref id="apache-lang" />
  |     <componentref id="apache-logging" />
  |     <componentref id="apache-modeler" />
  | ...
  |   </path>
  | 


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

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