Hi Felipe, Well, from my understanding, I'd say no. A provided dependency is more to be understood as a hint for packagings like war where the provided scoped dependency won't be included. But as described in the documentation you point to, this dependency is still on the compile AND test classpath.
Didn't you mix up runtime and provided scopes? I guess your problem is related to Eclipse limitations. For example, I seem to remember we recently had a failure in our CI server because runtime scoped dependency were added to the "Maven Dependencies" Eclipse classpath... This is kind of the same problem that the provided scope Cheers. PS : Note there's a dedicated user ml for m2eclipse. If problems you have are mainly connected to the UI or on the m2e internal management and not on maven itself, you should consider post there instead to have more reliable answers. 2008/12/22 Felipe Kamakura <[email protected]> > Hello everyone, > > 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? > > Thanks, and merry christmas to all, > > Felipe > > > > [1] > > http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html > -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
