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
dependecyMana
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: dev-unsubsc
Hi,
I am using Maven 3.0.x (2 or 3= and I have the following problem :
I use a parent POM with dependency management which is the good way to do this.
We are building for JBoss 4 and JBoss 6 and if for JBoss6 XercesImpl
is provided, for JBoss4 it is required with the Assembly Plugin.
So in my paren
