[Jboss-dev-forums] [Design of JBoss Build System] - Re: component-info.xml vs release.xml artifacts

[<rya...@jb...>]

The component-info allows other components to reference your artifacts.  It also allows you to create an artifactdef for that artifact in your jbossbuild.xml.    IE, it must be declared before it can be implemented.

The release.xml (toplevel build) dictates your release structure, as well as what jars should be downloaded upon synchronize.  However, it doesn't seem like you want these jars in your release and since you are building the remoting component from source, they won't be downloaded.  So in this case, there is no practical value in adding these artifacts to the component definition in your release.xml.  

That said, I think it's a good idea to keep these two in sync for now.  I realize that this duplication is evil.  I will detail in another thread where I think we should take the toplevel build.  But for now, we should move forward with what we have and keep these two component declarations in sync.

Regarding the includes element in the release.xml.  This was obsoleted by the component-info's export element.  You should remove this from your release.xml for *all* components.  I apologize for not doing this earlier as it just confuses the issue.  So your release.xml should look like this:


  |       <component id="remoting"
  |                  module="jboss-remoting"
  |                  version="5.0-SNAPSHOT"
  |       >
  |          <artifact id="jboss-remoting.jar" release="lib"/>
  |          <artifact id="jboss-remoting-tests.jar"/>
  |          <artifact id="jboss-remoting-loading-tests.jar"/>
  |       </component>
  |        <!-- no includes id=remoting-project here -->
  | 

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

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