I noticed the same thing. It's a bug. See also http://jira.codehaus.org/browse/MNG-514.
mike -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, June 27, 2005 9:08 AM To: [email protected] Subject: "provided" dependency scope I'm trying to figure out the correct approach here, and I may have also stumbled upon a bug... I'm using the "provided" scope for declaring dependencies, and I'm noticing that these libraries aren't included in the TEST classpath, so none of my tests compile. I tried adding the same dependencies again with a "test" scope, but it appears a dependency can only be loaded in one scope. When I add the dependencies as "compile" scope, everything works just fine, but then these huge jar files get put into my distribution jars when I package them, so that's not the scope I want either. Does anyone have advice on how to get around this? Or is it a bug? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
