Thanks Brian, that works nicely. Looking forward to it being released. Though I did think it kind of strange that it still provided this warning if the build is not forked, which it doesn't appear to be:
[WARNING] Removing: just-analyze from forked lifecycle, to prevent recursive invocation. Nor did I understand what this message means: [INFO] No goals needed for project - skipping Any ideas? William -----Original Message----- From: Brian E. Fox [mailto:[EMAIL PROTECTED] Sent: Tuesday, 24 July 2007 11:36 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 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 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
