Hi Henrik,
Henrik Niehaus wrote:
> Am 15.04.2010 14:54, schrieb Jörg Schaible:
[snip]
>> Please look into the POMs of the plugins and tell whether they declare a
>> dependency to another plugin themselves. If yes, which ones?
>>
>> - Jörg
>
> Hi Jörg,
>
> thanks for your answer. A colleague of mine seems to have better google
> skills than me and found ticket MNG-3506 a minute ago, which seems to be
> my problem. I have to wait until JIRA is back online to test the
> attached projects, but I think that is the problem.
>
> Nevertheless here are the plugin dependencies:
>
> warpath dependencies:
> * org.apache.maven:maven-plugin-api:2.0.4
> * org.apache.maven:maven-project:2.0.4
> * org.apache.maven:maven-artifact:2.0.4
> * org.apache.maven:maven-core:2.0.4
> * org.codehaus.plexus:plexus-utils:1.1
> * org.codehaus.plexus:plexus-utils:1.4.1
> * junit:junit:${junit.version}:test
> * maven-plugin-plugin (for reporting)
>
> private plugin:
> * org.apache.maven:maven-project:2.0.10
> * org.apache.maven:maven-archiver:2.2
> * ant:ant:1.6.5
I'd expect such effects also from plugins that derive from other ones.
However, that's not the case here. As workaround for MNG-3506 you might
simply share a common parent POM (note, that does not have to be physically
located in a parent directory, but is an artifact on its own), that declares
both plugins in the depMgmt section.
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
