>It's a common problem with dynamic instantiation.
>I understand why you skip runtime and test (test-runtime scope does not
>exist) scope.
>But what about the provide scope ? I think, by default, it should not
be
>skipped as for the compile scope.
Not sure. It seems like it should be included.
Hi Brian,
It's controlled by a flag you can turn on and off.
Yes, it's true. I haven't pay enough attention.
cf. ignoreNonCompile :
http://maven.apache.org/plugins/maven-dependency-plugin/analyze-mojo.html
The reason it's off by default is because you may have something required to
> run the te
To: Maven Developers List
Subject: Re: [maven-dependency-plugin] Analyze HTML Report
Very nice.
Brian, I wonder why the analyze goal of the maven-dependency-plugin just
take the compile dependencies for the Unused declared dependencies [1] ? Why
don't it take the test dependencies even though it
Very nice.
Brian, I wonder why the analyze goal of the maven-dependency-plugin just
take the compile dependencies for the Unused declared dependencies [1] ? Why
don't it take the test dependencies even though it also analyzes the test
classes ?
[1]
http://maven.apache.org/plugins/maven-dependency
Thanks Jeremy, I'll get that applied shortly.
-Original Message-
From: copernic Jeremy [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 14, 2007 10:26 AM
To: dev@maven.apache.org
Subject: [maven-dependency-plugin] Analyze HTML Report
I find the maven-dependency-plugin really powerful and
