Felipe Kamakura wrote: > > Recently I've noticed an inconsistency in M2Eclipse, and I wonder if this > behavior is normal or not: > > When I have a direct COMPILE dependency which in its turn declares a > PROVIDED dependency, this provided dependency should be ignored *[1]* in > my > main project right? But I noticed that this behavior doesn't happen inside > Eclipse. M2Eclipse does resolve the dependency and puts it in classpath. > This is bad because it gives me a false indication that everything is > compiling fine. > > Could someone enlight me? >
Felipe, this is documented at http://docs.codehaus.org/display/M2ECLIPSE/Dependency+Management Basically the "Maven Dependencies" container is assembled using "test" scope (because we do need to compile test code in Eclipse) and "provided' scope is included into the "test" scope. Also note that when you launch java app or junit test from Eclipse, class path would be constructed accordingly and it won't be the same as classpath used at compile time. regards, Eugene -- View this message in context: http://www.nabble.com/M2Eclipse-dependency-resolution-tp21128124p21132540.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
