You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Bryan Noll <bw...@gmail.com> on 2007/02/22 19:00:42 UTC

Finding where the jar came from...

Can anyone tell me the quick-n-dirty way to figure out which dependency 
is responsible for a jar that is being transitively downloaded/included 
in the project?  For instance, I see the servlet-api jar showing up in 
my assembly, but don't need it.  I've already excluded it once from the 
spring dependency like so:

        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring</artifactId>
            <version>2.0.2</version>
            <exclusions>
                <exclusion>
                    <groupId>javax.servlet</groupId>
                    <artifactId>servlet-api</artifactId>
                </exclusion>
            </exclusions>
        </dependency>



I just need to find out if another one of my dependencies depends on the 
servlet-api.  Could it be the case that the assembly plugin doesn't 
grock that I said to exclude when I specified the spring dependency?

TIA...

Bryan

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Finding where the jar came from...

Posted by Bryan Noll <bw...@gmail.com>.
Nevermind... I did it with a '-U' arg tacked on, and it worked...

Thanks again for the help.

Bryan Noll wrote:
> Thanks for the feedback.  I'm trying to use the project-info-reports 
> plugin, and am getting the following:
>
> org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 
> 'org.apache.maven.plugins:maven-project-info-reports-plugin' does not 
> exist or no valid version could be found
>
>
> ...which seems odd to me, because I can see it right here:
>
> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-project-info-reports-plugin/
>
>
> Any ideas?
>
> Alan D. Salewski wrote:
>> On Thu, Feb 22, 2007 at 11:00:42AM -0700, Bryan Noll spake thus:
>>   
>>> Can anyone tell me the quick-n-dirty way to figure out which dependency 
>>> is responsible for a jar that is being transitively downloaded/included 
>>> in the project?  For instance, I see the servlet-api jar showing up in 
>>> my assembly, but don't need it.  I've already excluded it once from the 
>>> spring dependency like so:
>>>
>>>        <dependency>
>>>            <groupId>org.springframework</groupId>
>>>            <artifactId>spring</artifactId>
>>>            <version>2.0.2</version>
>>>            <exclusions>
>>>                <exclusion>
>>>                    <groupId>javax.servlet</groupId>
>>>                    <artifactId>servlet-api</artifactId>
>>>                </exclusion>
>>>            </exclusions>
>>>        </dependency>
>>>
>>>
>>>
>>> I just need to find out if another one of my dependencies depends on the 
>>> servlet-api.  Could it be the case that the assembly plugin doesn't 
>>> grock that I said to exclude when I specified the spring dependency?
>>>     
>>
>> You can run
>>
>>     $ mvn -o project-info-reports:dependencies
>>
>> to generate the dependency report in target/site/dependencies.html
>>
>> HTH,
>>
>> -Al
>>
>>   

Re: Finding where the jar came from...

Posted by Bryan Noll <bw...@gmail.com>.
Thanks for the feedback.  I'm trying to use the project-info-reports 
plugin, and am getting the following:

org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 
'org.apache.maven.plugins:maven-project-info-reports-plugin' does not 
exist or no valid version could be found


...which seems odd to me, because I can see it right here:

http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-project-info-reports-plugin/


Any ideas?

Alan D. Salewski wrote:
> On Thu, Feb 22, 2007 at 11:00:42AM -0700, Bryan Noll spake thus:
>   
>> Can anyone tell me the quick-n-dirty way to figure out which dependency 
>> is responsible for a jar that is being transitively downloaded/included 
>> in the project?  For instance, I see the servlet-api jar showing up in 
>> my assembly, but don't need it.  I've already excluded it once from the 
>> spring dependency like so:
>>
>>        <dependency>
>>            <groupId>org.springframework</groupId>
>>            <artifactId>spring</artifactId>
>>            <version>2.0.2</version>
>>            <exclusions>
>>                <exclusion>
>>                    <groupId>javax.servlet</groupId>
>>                    <artifactId>servlet-api</artifactId>
>>                </exclusion>
>>            </exclusions>
>>        </dependency>
>>
>>
>>
>> I just need to find out if another one of my dependencies depends on the 
>> servlet-api.  Could it be the case that the assembly plugin doesn't 
>> grock that I said to exclude when I specified the spring dependency?
>>     
>
> You can run
>
>     $ mvn -o project-info-reports:dependencies
>
> to generate the dependency report in target/site/dependencies.html
>
> HTH,
>
> -Al
>
>   

Re: Finding where the jar came from...

Posted by "Alan D. Salewski" <as...@healthmarketscience.com>.
On Thu, Feb 22, 2007 at 11:00:42AM -0700, Bryan Noll spake thus:
> Can anyone tell me the quick-n-dirty way to figure out which dependency 
> is responsible for a jar that is being transitively downloaded/included 
> in the project?  For instance, I see the servlet-api jar showing up in 
> my assembly, but don't need it.  I've already excluded it once from the 
> spring dependency like so:
> 
>        <dependency>
>            <groupId>org.springframework</groupId>
>            <artifactId>spring</artifactId>
>            <version>2.0.2</version>
>            <exclusions>
>                <exclusion>
>                    <groupId>javax.servlet</groupId>
>                    <artifactId>servlet-api</artifactId>
>                </exclusion>
>            </exclusions>
>        </dependency>
> 
> 
> 
> I just need to find out if another one of my dependencies depends on the 
> servlet-api.  Could it be the case that the assembly plugin doesn't 
> grock that I said to exclude when I specified the spring dependency?

You can run

    $ mvn -o project-info-reports:dependencies

to generate the dependency report in target/site/dependencies.html

HTH,

-Al

-- 
:: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: ::
::
Alan D. Salewski
Software Developer
Health Market Science, Inc.
:: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: ::
:: 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Finding where the jar came from...

Posted by Dan Tran <da...@gmail.com>.
I think mvn site will give you the dependenecy report.

-D


On 2/22/07, Bryan Noll <bw...@gmail.com> wrote:
>
> Can anyone tell me the quick-n-dirty way to figure out which dependency
> is responsible for a jar that is being transitively downloaded/included
> in the project?  For instance, I see the servlet-api jar showing up in
> my assembly, but don't need it.  I've already excluded it once from the
> spring dependency like so:
>
>        <dependency>
>            <groupId>org.springframework</groupId>
>            <artifactId>spring</artifactId>
>            <version>2.0.2</version>
>            <exclusions>
>                <exclusion>
>                    <groupId>javax.servlet</groupId>
>                    <artifactId>servlet-api</artifactId>
>                </exclusion>
>            </exclusions>
>        </dependency>
>
>
>
> I just need to find out if another one of my dependencies depends on the
> servlet-api.  Could it be the case that the assembly plugin doesn't
> grock that I said to exclude when I specified the spring dependency?
>
> TIA...
>
> Bryan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>