Stefan Rademacher wrote:
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?
To mention an alternative, the dependency:analyze goal can be used to
check for "used and undeclared" dependencies. Admittedly not as
convenient as access rules but still helps to detect whether project
code reaches out to transitive dependencies instead of just direct ones.
Benjamin
[0]
http://maven.apache.org/plugins/maven-dependency-plugin/analyze-mojo.html
_______________________________________________
m2e-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/m2e-users
