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
