Using help:effective-pom it shows the 'correct', in term of Maven 3, scope which is not the expected scope. Whatever scope I set in my pom it is the scope defined (or not) in the parent pom's dependency management that is used. this is quite blocking as it means that you can't use the dependecyManagement with dependencies that might be used in other scopes.
On Mon, Mar 14, 2011 at 2:49 PM, Benjamin Bentmann <[email protected]> wrote: > Emmanuel Hugonnet wrote: > >> How can I display the genuine scope of my dependecy ? > > mvn -X ... > > The debug log will print the project dependency tree before the project gets > build. > > > Benjamin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
