Re: Why is dependency:analyze lying to me?

2014-02-14 Thread Mirko Friedenhagen
Hello, you see this a lot with runtime dependencies (which should probably be ignored during analyze anyway), so I mostly just ignore these in the output. It would be a cool thing, if you could suppress warnings for gavs directly in the analyze goal, so you see new stuff coming up more easily. Re

Re: Why is dependency:analyze lying to me?

2014-02-13 Thread Wayne Fay
> This may fall into the “How the hell is Maven supposed to know?” category, Yes, it most certainly does. > [WARNING] > org.springframework.security:spring-security-taglibs:jar:3.1.1.RELEASE:compile ... > Anyway, not sure if the plugin can be configured to detect these kind of > things, but a guy

Re: Why is dependency:analyze lying to me?

2014-02-13 Thread Paul Benedict
Especially if you use Spring XML configuration, it's impossible for the Dependency Plugin to figure out you need this-or-that Spring jar. The best you can do, actually, is use the new Spring Java Config so that your configuration is code and thus able to be statically analyzed. On Thu, Feb 13, 20

Re: Why is dependency:analyze lying to me?

2014-02-13 Thread laredotornado-3
Hi, This may fall into the “How the hell is Maven supposed to know?” category, but one of the dependencies that dependency:analyze lists when I run it on my WAR project is [WARNING] Unused declared dependencies found: … [WARNING] org.springframework.security:spring-security-taglibs:jar:3.1.1.R

Re: Why is dependency:analyze lying to me?

2014-02-12 Thread Barrie Treloar
On 13 February 2014 00:20, Mark H. Wood wrote: > On Wed, Feb 12, 2014 at 08:11:29AM +1030, Barrie Treloar wrote: > [snip] >> I think Maven is missing a scope, it needs to break up test into two >> phases; testCompile and testRuntime instead of having one scope which >> means both. [del] > Picky te

Re: Why is dependency:analyze lying to me?

2014-02-12 Thread Mark H. Wood
On Wed, Feb 12, 2014 at 08:11:29AM +1030, Barrie Treloar wrote: [snip] > I think Maven is missing a scope, it needs to break up test into two > phases; testCompile and testRuntime instead of having one scope which > means both. > This means that the analyze code can't tell what stuff is needed for

Re: Why is dependency:analyze lying to me?

2014-02-11 Thread Paul Benedict
I am so happy someone brought this up. I actually hit this issue several times but never got around to mentioning it. Please submit a JIRA issue! On Tue, Feb 11, 2014 at 3:41 PM, Barrie Treloar wrote: > On 12 February 2014 07:41, laredotornado-3 > wrote: > > Hi, > > > > I'm using Maven 3.1.1 o

Re: Why is dependency:analyze lying to me?

2014-02-11 Thread Barrie Treloar
On 12 February 2014 07:41, laredotornado-3 wrote: > Hi, > > I'm using Maven 3.1.1 on Mac 10.9.1. When I ran "mvn dependency:analyze" on > my project, I got results that included: > > [WARNING] Unused declared dependencies found: > ... > [WARNING]junit:junit:jar:4.11:te

Why is dependency:analyze lying to me?

2014-02-11 Thread laredotornado-3
Hi, I’m using Maven 3.1.1 on Mac 10.9.1. When I ran “mvn dependency:analyze” on my project, I got results that included: [WARNING] Unused declared dependencies found: … [WARNING]junit:junit:jar:4.11:test So I commented out the above junit dependency in my pom (declar