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:
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 MI
ECTED]
Sent: Tue 7/24/2007 12:21 AM
To: Maven Users List
Subject: dependency-plugin without forking
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 phas
Actually in the unreleased snapshot, there is a goal called (i think)
just-analyze that does exactly what you ask ;-)
From: William Ferguson [mailto:[EMAIL PROTECTED]
Sent: Tue 7/24/2007 12:21 AM
To: Maven Users List
Subject: dependency-plugin without forking
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]> w
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 causi
