The main build contains a declaration of the components that make up the
overall integration project:


  | <?xml version="1.0"?>
  | 
  | <!--
  |  JBoss, the OpenSource J2EE webOS
  |  
  |  Distributable under LGPL license.
  |  See terms of license at gnu.org.
  | -->
  | <project name="main.build"
  |          default="build" 
  |          basedir="."
  | >
  |    <!-- Import the types -->
  |    <import file="../tools/jboss/tasks.xml"/>
  | 
  |    <!-- The test classpath -->
  |    <includes id="test.path">
  |       <include input="junit.jar"/>
  |    </includes>
  | 
  |    <!-- The build -->
  |    <build id="JBossAS" 
  |           version="5.0.0alpha"
  |           description="JBoss Application Server"
  |           targetdefs="targets">
  | 
  |       <component id="jboss">
  |          <artifact id="jboss-common.jar"
  |                    
location="file:///home/ejort/jboss-head/workspace/common/output/lib/jboss-common.jar"
  |          />
  |       </component>
  | 
  |       <component id="junit">
  |          <artifact id="junit.jar"
  |                    
location="file:///home/ejort/jboss-head/workspace/thirdparty/junit-junit/lib/junit.jar"
  |          />
  |       </component>
  | 
  |       <component id="test1">
  |          <artifact id="test1.jar" release="lib"/>
  |          <artifact id="test1.api"/>
  |       </component>
  | 
  |       <component id="test2">
  |          <artifact id="test2.jar" release="lib"/>
  |          <artifact id="test2.api"/>
  |       </component>
  |    </build>
  | 
  | </project>
  | 

build - defines what you are building
component - defines the subprojects which might be thirdparty rather than local 
projects
artifact - defines what you expect to come out of the component and where it 
should be placed in the integration release structure.

Like I said, I didn't do too much work on the thirdparty/download stuff.
But you can imagine that it can contain the location of the components
that maybe urls or cvs checkout parameters.

I would imagine that the location would contain the version of the jar in the 
url?
I would also image that most of the CVS parameters would be common
and actually defined in the , e.g. the CVSROOT and the tag.

You can ignored the  this just works to define a common classpath
in this case the jars required for running tests.

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

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


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to