[Jboss-dev-forums] [Design of JBoss Build System] - Requirements - Top level build - structure

[<ad...@jb...>]

I'll state the requirements through use cases and then we can move
to something more concrete like defining a schema for each configuration.
The xml will be pseudo for now.

The basics of the top level build are to define some information about what we are
building and the primary components that make up the build.
It should provide enough information to be able to bootstrap the rest of the build.

I'm going to ignore versioning for now and deal with that as a separate
cross cutting concern on a different topic, but there will obviously be
some overlap.

Trivial example:

  | <project>
  |    <info id="jbossas"
  |             description=JBoss Application Server"
  |             repository="http://repository.jboss.com"
  |             cvsroot="cvs.forge.jboss.com/cvsroot/jboss"
  |    </info>
  |    <component name="naming"/>
  |    <component name="transaction"/>
  |    <component name="server"/>
  |    etc.
  | </project>
  | 

Standalone example:

  | <project>
  |    <info id="jbosscache"
  |             description="JBoss Cache"
  |             repository="http://repository.jboss.com"
  |             cvsroot="cvs.forge.jboss.com/cvsroot/jboss"
  |    </info>
  |    <component name="jbosscache"/>
  | </project>
  | 

Federated example:

  | <project>
  |    <info id="portal"
  |             description="JBoss Portal"
  |             repository="http://repository.jboss.com"
  |             cvsroot="cvs.forge.jboss.com/cvsroot/portal"
  |    </info>
  |    <extends name="jbossas"/>
  |    <component name="bb"/>
  |    <component name="wiki"/>
  |    etc.
  | </project>
  | 


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

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