add a configuration to the plugin directly not nested within an execution.
that will modify the defaults for all executions.
you may then need to add in the configuration sections for each execution
the config to switch back from your defaults.
Also, this kind of question is better suited to the users list.
The dev list is really for people developing Maven (and maven plugins) not
for people developing with Maven (who are really users)
On Thu, Sep 11, 2008 at 9:47 AM, Barrie Treloar <[EMAIL PROTECTED]> wrote:
> This will teach me to write before I've fully checked everything.
> I had <skip>true</true> on so I could check the configurations.
>
> What this configuration gives is three executions of surefire:
> [INFO] [surefire:test]
> ...
> [INFO] [surefire:test {execution: test}]
> ...
> [INFO] [surefire:test {execution: integration-test}]
>
> Which is not what is wanted. the execution "test" should be the default
> one.
> If the id section is removed, then the execution's configuration
> doesn't appear to affect the default surefire:test.
>
> The only way I could see to fix this was to remove the execution block
> and use the plugin's configuration section.
> The problem with this is that the run-its profile will now include
> those values too.
> The workaround is to explicitly specify the values in the profile to
> override the default's values.
>
> Is this the best way?
> If I could override the default executions configuration somehow that
> would be rhe way to go.
> I can't find any docs to explaun this better anywhere.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
