The analyze goal has already been merged into the plugin and is the same here... it does the class level analysis. There is also analyze-dep-mgt to do the 1577 check. Analyze will do both so there's no clash here. Take a look at the site: http://maven.apache.org/plugins/maven-dependency-plugin/
-----Original Message----- From: Jörg Schaible [mailto:[EMAIL PROTECTED] Sent: Monday, March 19, 2007 8:10 AM To: Maven Developers List Subject: RE: [VOTE] maven-dependency-plugin 2.0-alpha-3 Max Bowsher wrote on Monday, March 19, 2007 12:00 PM: > Jörg Schaible wrote: >> It is very unfortunate, that you took the same goal that was >> introduces by the maven-dependency-analyzer-plugion, that is >> currently merged in the sandbox in a branch. > > TTBOMK, ?? > it is not possible for one plugin to implement > foobar:alpha and > another to implement foobar:beta - the prefix must map to a single > plugin, no? > > So, it would be impossible for one plugin to take the goal of another. No, the maven-dependency-analyzer-plugin has been merged into the maven-dependency-plugin in the sandbox and obviouskly no plugin can support two different tasks with the same goal. - Jörg --------------------------------------------------------------------- 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]
