its my experience that maven2 configures a plugin on first encounter.
I had similar problems using the antrun plugin with different
subprojects requiring different ant deps. I had to put the antrun
plugin config in the root projects pom with all the deps. I was
getting different behaviours depending on whether I invoked mvn in the
root or the subproject. This is on 2.0.8, 2.0.9 and 2.0.10. I vaguely
recall someone raising an issue on this.
come back maven1 all is forgiven :-)
Martin West
On 27 May 2009, at 15:21, Matt Wringe wrote:
> On Tue, 2009-05-26 at 12:28 +0200, Alexander Brill wrote:
>> Hi,
>>
>> I have a parent pom where I have defined my cargo plugin
>> configuration
>> for Maven2 which several of our projects use.
>>
>> However, one of our projects have an extra dependency which I don't
>> want included into the other projects. So I'd like to append this
>> extra dependency to the projects pom.
>>
>> But trying to reconfigure the plugin overwrites all the other
>> dependencies, so I only get mygroup:myartifact included, all other
>> are
>> removed. Is there a way to accomplish what I want?
>
> Can any maven experts help out here?
>
>>
>> <plugin>
>> <groupId>org.codehaus.cargo</groupId>
>> <artifactId>cargo-maven2-plugin</artifactId>
>> <configuration>
>> <container>
>> <dependencies>
>> <dependency>
>> <artifactId>myartifact</artifactId>
>> <groupId>mygroup</groupId>
>> </dependency>
>> </dependencies>
>> </container>
>> </configuration>
>> </plugin>
>>
>>
>> --
>> Alexander Brill
>>
http://brill.no>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>
http://xircles.codehaus.org/manage_email>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email