You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Gabriele Contini <gc...@hotpop.com> on 2007/01/24 13:04:39 UTC
transitivity path to resolved dependency
Hi,
we have a project structure with many modules and inherited dependencies.
How can we find out the transitivity path for any given dependency? For
example :
Path to dependency:
1) fop:fop:jar:0.20.5
2) xalan.xalan:jar:2.4.1
This information is usually displayed only for unresolved dependencies,
is it possible to have it for resolved dependencies too ?
We looked into the dependency:resolve goal but we could not find any
option to display this information.
Gabriele and Luca
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: transitivity path to resolved dependency
Posted by Gabriele Contini <gc...@hotpop.com>.
Petar Tahchiev wrote:
> On 24/01/07, Gabriele Contini <gc...@hotpop.com> wrote:
>>
>> Hi,
>> we have a project structure with many modules and inherited
>> dependencies.
>> How can we find out the transitivity path for any given dependency? For
>> example :
>>
>> Path to dependency:
>> 1) fop:fop:jar:0.20.5
>> 2) xalan.xalan:jar:2.4.1
>>
>> This information is usually displayed only for unresolved dependencies,
>> is it possible to have it for resolved dependencies too ?
>> We looked into the dependency:resolve goal but we could not find any
>> option to display this information.
>>
>> Gabriele and Luca
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>> This is my method of keeping the track of transitive dependencies.
>
> Delete the artifact (in your case xalan) from yuor local repository
> and run
> mvn install -o
> This tells maven to run the build offline, and since you don't have the
> dependency in your repo
> when another dependency tries to add it to your local repo. it would
> fail on
> that place.
>
> Maybe there is a better way, but I have always used this.
>
Ugly, but it works! thank you a lot!! :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: transitivity path to resolved dependency
Posted by Petar Tahchiev <pa...@gmail.com>.
On 24/01/07, Gabriele Contini <gc...@hotpop.com> wrote:
>
> Hi,
> we have a project structure with many modules and inherited dependencies.
> How can we find out the transitivity path for any given dependency? For
> example :
>
> Path to dependency:
> 1) fop:fop:jar:0.20.5
> 2) xalan.xalan:jar:2.4.1
>
> This information is usually displayed only for unresolved dependencies,
> is it possible to have it for resolved dependencies too ?
> We looked into the dependency:resolve goal but we could not find any
> option to display this information.
>
> Gabriele and Luca
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
> This is my method of keeping the track of transitive dependencies.
Delete the artifact (in your case xalan) from yuor local repository and run
mvn install -o
This tells maven to run the build offline, and since you don't have the
dependency in your repo
when another dependency tries to add it to your local repo. it would fail on
that place.
Maybe there is a better way, but I have always used this.
--
Regards, Petar!
Karlovo, Bulgaria.