Hi,
thanks for the answer, but my Mojo explicitly needs the merged
configuration. Just not by replacing the list elements, but by adding
them.
Sorry that my first post was misleading. Here's an example:
Configuration from parent pom:
<configuration>
<warnings>
<warning>all</warning>
</warnings>
<configuration>
Configuration from the child pom:
<configuration>
<warnings>
<warning>insane</warning>
</warnings>
<configuration>
Wanted configuration:
<configuration>
<warnings>
<warning>all</warning>
<warning>insane</warning>
</warnings>
<configuration>
Instead, I get only the child configuration. Is there a way to get a
"correct" merged config in my Mojo?
Regards,
Jochen
On 2006-11-23 18:51:59 +0100, "Brian E. Fox" <[EMAIL PROTECTED]> said:
You need to put them in a separate <executions> tag and use a different
id. If you don't specify an execution, then it uses the default one and
will merge the config.
-----Original Message-----
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Jochen Kuhnle
Sent: Thursday, November 23, 2006 8:51 AM
To: dev@maven.apache.org
Subject: Merging list properties in plugin configurations?
Hi,
I am writing some plugins that have list properties, e.g.:
<warnings>
<warning>all</warning
<warning>special</warning
<warning>etc.</warning
</warnings>
I now want to have different configurations (through parents, profiles,
etc.), but when merging, Maven2 only keeps entries from one
configuration (see
DefaultPluginManager.buildTopDownMergedConfiguration). Is there a way
around this?
Regards,
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional
commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
