Adrian,

The Class-Path for a jar is now included in the build path, not just for 
testing.  I think this may be a problem, because I am not forced to specify a 
direct dependency if it is a dependency for another artifact.

Example is jmx.  I can compile JMX using just these declared dependencies:


  |       <source id="main">
  |          <include input="common-project"/>
  |          <include input="bcel"/>
  |          <include input="junit"/>
  |       </source>
  | 

and then the Class-Path from jboss-common.jar is expanded into my build path:


  |   <classpath>
  |     <pathelement 
location="C:\projects\jboss-head\thirdparty\apache-xerces\lib\xercesImpl.jar"/>
  |     <pathelement 
location="C:\projects\jboss-head\thirdparty\junit-junit\lib\junit.jar"/>
  |     <pathelement location="C:\projects\jboss-head\jmx\output\classes\main"/>
  |     <pathelement 
location="C:\projects\jboss-head\thirdparty\apache-jaxme\lib\jaxmexs.jar"/>
  |     <pathelement 
location="C:\projects\jboss-head\thirdparty\apache-bcel\lib\bcel.jar"/>
  |     <pathelement 
location="C:\projects\jboss-head\thirdparty\wutka-dtdparser\lib\dtdparser121.jar"/>
  |     <pathelement 
location="C:\projects\jboss-head\thirdparty\apache-commons\lib\commons-httpclient.jar"/>
  |     <pathelement 
location="C:\projects\jboss-head\thirdparty\oswego-concurrent\lib\concurrent.jar"/>
  |     <pathelement 
location="C:\projects\jboss-head\thirdparty\gnu-regexp\lib\gnu-regexp.jar"/>
  |     <pathelement 
location="C:\projects\jboss-head\common\output\lib\jboss-common.jar"/>
  |     <pathelement 
location="C:\projects\jboss-head\thirdparty\dom4j-dom4j\lib\dom4j.jar"/>
  |     <pathelement 
location="C:\projects\jboss-head\thirdparty\apache-slide\client\lib\webdavlib.jar"/>
  |     <pathelement 
location="C:\projects\jboss-head\common\output\lib\namespace.jar"/>
  |     <pathelement 
location="C:\projects\jboss-head\thirdparty\apache-log4j\lib\log4j.jar"/>
  |  </classpath>
  | 
  | 

This is undesirable because I jmx has direct dependencies on jars which are not 
documented in the input.  This is fine for testing, but not in building where 
we want the build to fail if direct dependencies are not documented explicitly.

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

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


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to