For the export functionality, we want to keep the syntax as simple as possible.
So to include the jmx project in your classpath you would want to do:
<source id="main">
| <include component="jmx"/>
| </source>
This would look for a component-info.xml first in ../jmx and then in
../thirdparty/jmx. The component-info would need to have an export declaration:
<component id="jmx" ... >
| <artifact id="jboss-jmx.jar"/>
| <artifact id="jboss-jmx-core.jar"/>
| <export>
| <include input="jboss-jmx.jar"/>
| </export>
| </component>
So that jboss-jmx.jar would be included in the classpath of the compilation.
However, I think you will still want the ability to use artifacts or other
includes besides the exported ones:
<source id="main">
| <include component="jmx" input="jboss-jmx-core.jar"/>
| </source>
| This would cause the parsing as above, but would use the designated
reference id instead of the component's exports. So the export statement is
the default, but you retain the ability to reference an abitrary input.
To do this, I will need to add a component-info.xml for thirdparty/* in cvs. I
assme there is no problem with this? We'll need these eventually, anyway.
Basically, it will involve copying the existing thirdparty component
declarations from jbossas/jbossbuild.xml into the component-info.xml and
changing the {includes} to {export}.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872967#3872967
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872967
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development
