Hi, we are currently moving our complete build management from Ant to Maven. One advantage now is the strong dependency management, especially for transitive dependencies. But within eclipse, there is a big downside, that we didn't see before: The code completion allows every developer to use classes from any transitive dependency, even though it isn't explicitly declared in our pom. An example: An open source library uses Google Guava internally, but we - for some reason - don't want to use it in our code. The "Maven Dependencies" in Eclipse contain Google Guava, because it is needed by that 3rd party library, and is consequently also offered in the Eclipse code completion. Is there a way to tell m2e to restrict the access only to the direct dependencies, declared in our pom.xml? Maybe by generating Eclipse access rules for the "Maven Dependencies" Classpath Container? Thank you very much and best regards Stefan
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
