> What you could possibly do is create a profile that you would use for > compiling. In this profile, add the problem dependencies with scope of > "compile". But in the main part, add the problem dependencies with scope of > "runtime", so that projects which just *use* your code (via its pom) see the > lib as just a runtime dependency, not a compiletime one. > > I'm not sure if it's possible to have the same dependency twice (which will > happen when the profile is active) but it might be worth trying..
I'm not sure either, but I would assume the least-restrictive scope would "win". So if you specify compile and runtime, you'll get compile. If anything else happens, I might be inclined to call it a bug, or I'd like someone to explain what they're thinking. Try mvn help:effective-pom -pYOUR_PROFILE_NAME to see what Maven actually does with the multiple dependency declarations. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
