In that case - I would imagine that the plugin should cause the build to fail if it does not meet certain metrics - if the new goal does not do this, it'd be a useful addition.
Eric On 7/24/07, William Ferguson <[EMAIL PROTECTED]> wrote:
Hi Eric, The use case is that we would like to ensure that the dependencies are the minimal set of the appropriate dependencies as an integral part of our build. Ie part of our quality bar. But looks like I'm not alone, as Brian pointed out dependency-plugin:2.0-alpha-5-SNAPSHOT has the just-analyze Mojo which does exactly what I need. William -----Original Message----- From: Eric Redmond [mailto:[EMAIL PROTECTED] Sent: Tuesday, 24 July 2007 11:22 PM To: Maven Users List Subject: [***POSSIBLE SPAM***] - Re: dependency-plugin without forking - Email has different SMTP TO: and MIME TO: fields in the email addresses dependency:analyze is meant to help people check their project dependencies occasionally and fix accordingly? What use-case do you have for requiring it to run every time? If you just want a print-out, there is always the dependency report. Eric On 7/23/07, William Ferguson <[EMAIL PROTECTED]> wrote: > > Is it possible execute dependency:analyze without having the > dependency-plugin fork the build? > > We'd really like to have dependency:analyze execute as part of every > build, but having all the phases execute twice is not going to be > acceptable. Is there a way to stop the depdendency-plugin from causing > the phases to execute again? > > We are using maven-dependency-plugin:2.0-alpha-4 and maven-2.0.7 > > William > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Eric Redmond http://blog.propellors.net --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Eric Redmond http://blog.propellors.net
