You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Giovanni Azua <br...@swissonline.ch> on 2008/08/24 20:12:17 UTC
dependency tree but for build/reporting plugins
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 understand where they are coming from. I believe this is
the reason why I still get MSITE-274.
TIA,
Regards,
Giovanni
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: dependency tree but for build/reporting plugins
Posted by Vincent Siveton <vi...@gmail.com>.
Hi
2008/8/27 Giovanni Azua <br...@swissonline.ch>:
> Hi Dennis,
>
> I swept my local repo first and then ran the build as you recommended using
> the -X option.
>
> These are all the doxia versions that end up being downloaded into my local
> repo:
> 1.0-alpha-7
maven-reporting-api-2.0.5 uses doxia-api 1.0-alpha-7
> 1.0-alpha-8
given from findbugs-maven-plugin
> 1.0-alpha-9
from maven-changes-plugin
> 1.0-alpha-10
> 1.0-alpha-11
from site plugin
HTH
Vincent
> But from the build log alone I can't figure out why the e.g. 1.0-alpha-10
> gets pulled. I added the build.log output file for this last build tentative
> and would appreciate enormously if you could have a look at it to see why
> the non 11 doxia versions get downloaded and further how to fix this:
> <http://perfectjpattern.svn.sourceforge.net/viewvc/perfectjpattern/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:dennisl@apache.org]
>> 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.
>>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: dependency tree but for build/reporting plugins
Posted by Giovanni Azua <br...@swissonline.ch>.
Hi Dennis,
I tried commenting out not only the Clover plugin but all the reporting
plugins and I get a fundamentally different behavior than in your setup ...
I still get at least the doxia versions alpha 7 and 10 pulled on top of 11.
Did you use the build script? Or otherwise what exact command did you use?
What was your settings.xml? I mean the relevant snippets e.g. did you enable
Snapshot repositories?
What were your Java and Maven versions?
Many thanks in advance,
Best regards,
Giovanni
> -----Original Message-----
> From: Dennis Lundberg [mailto:dennisl@apache.org]
> Sent: 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 see if it is the
> problem.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: dependency tree but for build/reporting plugins
Posted by Dennis Lundberg <de...@apache.org>.
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 see if it is the
problem.
Giovanni Azua wrote:
> Hi Dennis,
>
> I swept my local repo first and then ran the build as you recommended using
> the -X option.
>
> These are all the doxia versions that end up being downloaded into my local
> repo:
> 1.0-alpha-7
> 1.0-alpha-8
> 1.0-alpha-9
> 1.0-alpha-10
> 1.0-alpha-11
>
> But from the build log alone I can't figure out why the e.g. 1.0-alpha-10
> gets pulled. I added the build.log output file for this last build tentative
> and would appreciate enormously if you could have a look at it to see why
> the non 11 doxia versions get downloaded and further how to fix this:
> <http://perfectjpattern.svn.sourceforge.net/viewvc/perfectjpattern/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:dennisl@apache.org]
>> 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.
>>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: dependency tree but for build/reporting plugins
Posted by Giovanni Azua <br...@swissonline.ch>.
Hi Dennis,
I swept my local repo first and then ran the build as you recommended using
the -X option.
These are all the doxia versions that end up being downloaded into my local
repo:
1.0-alpha-7
1.0-alpha-8
1.0-alpha-9
1.0-alpha-10
1.0-alpha-11
But from the build log alone I can't figure out why the e.g. 1.0-alpha-10
gets pulled. I added the build.log output file for this last build tentative
and would appreciate enormously if you could have a look at it to see why
the non 11 doxia versions get downloaded and further how to fix this:
<http://perfectjpattern.svn.sourceforge.net/viewvc/perfectjpattern/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:dennisl@apache.org]
> 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.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: dependency tree but for build/reporting plugins
Posted by Dennis Lundberg <de...@apache.org>.
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. needed for build and reporting.
>
> My problem is that upon building I get zillion of doxia versions pulled out,
> and I would like to understand where they are coming from. I believe this is
> the reason why I still get MSITE-274.
>
> TIA,
> Regards,
> Giovanni
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org