Is there a way to specify a dependency to be available for compilation and test running, but not have it packaged up?
We have a situation where some older code that has been converted to maven2 uses a library (SAP JCo if anyone is familiar with it) that must be there to compile and also to run. Some of the tests were written to communicate with SAP, which requires the jar to be in the classpath at runtime. When the application is deployed the jar is provided via the container, so we need it available to run the tests, but don't want it packaged up with the application. Jason Porter O.C. Tanner Information Services Technical Specialist --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
