JBoss development, A new message was posted in the thread "EJBTHREE-1998: TestSuite Client Dependencies from JBOSS_HOME": http://community.jboss.org/message/525315#525315 Author : jaikiran pai Profile : http://community.jboss.org/people/jaikiran Message: -------------------------------------------------------------- Any specific reason why we are adding individual jars from the JBOSS_HOME to the classpath, instead of just adding the JBOSS_HOME/client folder to the classpath. Something like this, which i did to get the testcases passing:   [jpai@localhost testsuite]$ svn diff build-test.xml Index: build-test.xml =================================================================== --- build-test.xml      (revision 100789) +++ build-test.xml      (working copy) @@ -325,6 +325,7 @@    <path id="client.classpath">      <!-- JBoss Client Binaries --> +    <fileset dir="${location.client.lib}" includes="*.jar"/>      <pathelement path="${location.client.lib.commons-logging}" />      <pathelement path="${location.client.lib.jbossall}" />      <pathelement path="${location.client.lib.jbossxb}" />   Ideally, it should have been just JBOSS_HOME/client/jbossall-client.jar. But i see that the MANIFEST.MF of that jar is incomplete. So why not just JBOSS_HOME/client/*.jar. That way, we don't have to keep changing our build file if the jar file names changes (like in this SNAPSHOT case).   If there are no objections, then i'll commit this patch (and also remove any subsequent, redundant pathelements from the classpath). -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/525315#525315