[m2e-users] Dependency scope and Eclipse classpath resolution

[Stanimir Stamenkov <s7an10@xxxxxxxxxxxx>]

I notice the "Maven Dependencies" container resolves "runtime" scope 
dependencies for compilation which allows one to use them 
erroneously while writing code in Eclipse.  This will reveal the 
error later, when building from the command-line.  Is it possible 
the "Maven Dependencies" container resolve different set of 
dependencies, depending whether it is used for compilation or in a 
Run configuration?

I would also like to see an option to resolve only declared 
dependencies for compilation and not their transitive dependencies, 
e.g. using the dependency:analyze goal one could get warnings like 
"Used undeclared dependencies found" - it would be nice not to 
present those in the Eclipse classpath in first place.  At the very 
least - option to generate corresponding waring in Eclipse would be 
nice.

--
Stanimir