You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Barry Kaplan <gr...@memelet.com> on 2008/09/15 17:20:07 UTC
dependency:analyze-only and pom-only dependencies
We have setup some poms only for the purpose of declaring dependencies (eg,
"unit-test" which depends junit, hamcrest, mockito, etc). Dependent projects
declare the dependency using "<type>pom</type>".
When I perform dependency:analyze-only on a project that depends on this pom
"unit-test" is marked as "Unused declared dependencies found".
Is there a way for maven to not get confused in this case?
--
View this message in context: http://www.nabble.com/dependency%3Aanalyze-only-and-pom-only-dependencies-tp19495150p19495150.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: dependency:analyze-only and pom-only dependencies
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
This is because the analyze component is looking for classes in your
dependency that are referenced in your classes. We should skip pom
dependencies.
On 9/21/08 8:16 PM, "Brett Porter" <br...@gmail.com> wrote:
> This seems like a limitation in the plugin that you should file an issue for.
>
> Cheers,
> Brett
>
> 2008/9/16 Barry Kaplan <gr...@memelet.com>:
>>
>> We have setup some poms only for the purpose of declaring dependencies (eg,
>> "unit-test" which depends junit, hamcrest, mockito, etc). Dependent projects
>> declare the dependency using "<type>pom</type>".
>>
>> When I perform dependency:analyze-only on a project that depends on this pom
>> "unit-test" is marked as "Unused declared dependencies found".
>>
>> Is there a way for maven to not get confused in this case?
>> --
>> View this message in context:
>> http://www.nabble.com/dependency%3Aanalyze-only-and-pom-only-dependencies-tp1
>> 9495150p19495150.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> 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:analyze-only and pom-only dependencies
Posted by Brett Porter <br...@gmail.com>.
This seems like a limitation in the plugin that you should file an issue for.
Cheers,
Brett
2008/9/16 Barry Kaplan <gr...@memelet.com>:
>
> We have setup some poms only for the purpose of declaring dependencies (eg,
> "unit-test" which depends junit, hamcrest, mockito, etc). Dependent projects
> declare the dependency using "<type>pom</type>".
>
> When I perform dependency:analyze-only on a project that depends on this pom
> "unit-test" is marked as "Unused declared dependencies found".
>
> Is there a way for maven to not get confused in this case?
> --
> View this message in context: http://www.nabble.com/dependency%3Aanalyze-only-and-pom-only-dependencies-tp19495150p19495150.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org