Good day to you, martin, I'm guessing that happened while maven was building module B. AFAIK, that's just a reminder that that jar is using the scope "test" only. I don't think it's anything to worry about ( not unless you did not specify that jar to be of scope "test" ).
Cheers, Franz matinh wrote: > > Hi all! > > I've got a question regarding dependencies. Let me first explain my > project structure. > > - I've got project A which is a web application (WAR). > - A depends on project B which is of type JAR. > - B depends on hibernate which has an optional dependency on ehcache. > > My idea is if A wants to use hibernate's second level cache ehcache A has > to define a dependency on ehcache. To use ehcache also for tests in B, B > defines ehcache as a dependency of scope "test". > > Whenever I now run mvn test I get the following warings: > > | Artifact net.sf.ehcache:ehcache:jar:1.2.3:test retains local scope > 'test' overriding broader scope 'compile' > | given by a dependency. If this is not intended, modify or remove the > local scope. > > How can I get rid of this warning? Or am I doing something wrong? > > tia, > - martin > -- > Martin Höller | [EMAIL PROTECTED] > *x Software + Systeme | http://www.xss.co.at/ > Karmarschgasse 51/2/20 | Tel: +43-1-6060114-30 > A-1100 Vienna, Austria | Fax: +43-1-6060114-71 > > > -- View this message in context: http://www.nabble.com/handling-of-optional-3rd-party-dependencies-in-tests-tf3226679s177.html#a8963739 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
