No, Class-Path references are not treated as deployables as per the spec now.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Brian Wallis" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, March 12, 2003 3:32 PM Subject: [JBoss-user] 3.0.4 -> 3.0.7 deployment dependencies change? I was building on 3.0.4 and have changed to 3.0.7. To resolve dependencies between jars I had Class-Path entries in the Manifests of the jars like so... in JavaCommon.jar META-INF/MANIFEST.MF there is an entry: Class-Path: Cis.jar which with 3.0.4 caused Cis.jar to be deployed before the deployment of JavaCommon.jar was completed thus making the classes in Cis.jar available during the deployment of JavaCommon.jar. This no longer seems to work with 3.0.7. This did seem to be a reasonable way to define dependencies between jar files, is this not a good way to do it? Is there a better way or is 3.0.7 broken? thanks, brian wallis... ------------------------------------------------------- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
