On Thu, Sep 11, 2008 at 12:52 PM, Barrie Treloar <[EMAIL PROTECTED]> wrote:
> On Thu, Sep 11, 2008 at 6:43 PM, Stephen Connolly
> <[EMAIL PROTECTED]> wrote:
> > 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 6:43 PM, Stephen Connolly
<[EMAIL PROTECTED]> wrote:
> 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
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
This will teach me to write before I've fully checked everything.
I had 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-
I see the problem now.
Since there is no block BOTH the build.plugin and the profile
section have the same id of "default".
Hence when -Prun-its is on, the profile section overwrites the
build.plugin section.
(Special thanks to help:effective-pom).
Since the point of the run-its profile is to ru
I forgot to mention that there is also a profile, and I am assuming
the base configuration that includes memory and property settings
should also be included in the profile as well.
Otherwise I would just merge the two sections together.
run-its
ma
Here is the configuration.
maven-surefire-plugin
test
**/*Test.java
**/projects/**
