I'm doing this from memory but I think the site plugin produces such a report.
On 3/6/08, EJ Ciramella <[EMAIL PROTECTED]> wrote: > That's what I tried initially, but it doesn't complaine about where > exactly the mis-matched versions are (as well as being bound to the > verify stage). > > Did I miss the boat a bit here? > > -----Original Message----- > From: deckrider [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 06, 2008 9:57 PM > To: Maven Users List > Subject: Re: Validating version selections > > Perhaps a pom depending on those other projects? Then you could run > the dependency plugin against it. > > > > On 3/6/08, EJ Ciramella <[EMAIL PROTECTED]> wrote: > > Is there a standalone type plugin one can use to verify that multiple > > projects are using the same set of dependencies? > > > > I'd love to use something like dependency-analyze, but I want to > compare > > two different deployable units (rather than having each deployable > unit > > validate it's own set of dependencies). > > > > > -- > ASCII ribbon campaign: > () against HTML email > /\ against Microsoft attachments > Information: http://www.expita.com/nomime.html > > --------------------------------------------------------------------- > 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] > > -- ASCII ribbon campaign: () against HTML email /\ against Microsoft attachments Information: http://www.expita.com/nomime.html --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
