g [mailto:[EMAIL PROTECTED]
>> Sent: Sunday, August 24, 2008 8:17 PM
>> To: Maven Users List
>> Subject: Re: dependency tree but for build/reporting plugins
>>
>> Run Maven with the -X command line switch to reveal all dependencies and
>> how they are pulled in.
Wednesday, August 27, 2008 9:10 PM
> To: Maven Users List
> Subject: Re: dependency tree but for build/reporting plugins
>
> When I tried you project locally I noticed that the Clover plugin pulled
> in 1.0-alpha-10. You could try commenting that out to se
ttern/trunk/bui
> ld.log>
>
> My parent pom is under:
> <http://perfectjpattern.svn.sourceforge.net/viewvc/perfectjpattern/trunk/pom
> .xml?view=markup>
>
> TIA,
> Regards,
> Giovanni
>
>
>> -Original Message-
>> From: Dennis Lundberg [mailto:[EMAIL
gust 24, 2008 8:17 PM
> To: Maven Users List
> Subject: Re: dependency tree but for build/reporting plugins
>
> Run Maven with the -X command line switch to reveal all dependencies and
> how they are pulled in.
>
Run Maven with the -X command line switch to reveal all dependencies and
how they are pulled in.
Giovanni Azua wrote:
> hi,
>
> The command "mvn dependency:tree" gives me an overview of all dependencies
> for my project. I would like to see the same but for the referenced maven
> plugins i.e. nee
hi,
The command "mvn dependency:tree" gives me an overview of all dependencies
for my project. I would like to see the same but for the referenced maven
plugins i.e. needed for build and reporting.
My problem is that upon building I get zillion of doxia versions pulled out,
and I would like to un