To see a real life example:
check out http://svn.apache.org/repos/asf/maven/release/trunk
try to run ONLY MRELEASE-459 ( under /src/it/projects/perform ) without
shifting execution-blocks within the pom. You should use something like
-Dinvoker.test=
Robert
Op Mon, 27 May 2013 07:24:39 +0200 schreef Brett Porter <[email protected]>:
For some reason I'm not grokking the use case, but I can comment on the
syntax anyway...
On 26/05/2013, at 1:31 PM, Robert Scholte <[email protected]> wrote:
Hi,
I'm facing an issue with the includes/excludes for the
maven-invoker-plugin which needs a Maven-wide solution where
includes/excludes are used.
When having several execution-blocks, each with its own includes, then
I can't use -Dinvoker.test=sometestA, sometestB anymore, because it
will be used for every execution-block, causing most of the tests to
fail.
I'm looking for something like -Dinvoker.test=<someTestA,someTestB> or
[someTestA,someTestB], so these tests are only executed if they are a
subcollection of the includes/excludes of the execution-block.
Would a different parameter for this be appropriate? e.g.
-Dinvoker.test.in=someTestA,someTestB
The '<>'-markup has the disadvantage that it can't be used within the
pom without being escaped, but I think this markup should primary be
used on cmdline.
That's even worse on the command line :)
The '[]' and '()'-markup reflect ranges, I don't think that's correct
here.
'{}'-markup is related to expressions.
Personally I'd use () for a set. While they do have a special meaning
when describing an interval, they're also used to describe sets. That
said, they (as with the others) can cause some grief for shell scripts
or quoting, so if you can avoid them it's probably better.
- Brett
--
Brett Porter
[email protected]
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
http://twitter.com/brettporter
---------------------------------------------------------------------
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]
