Hi Robert,
On 11/9/15 10:48 PM, Robert Scholte wrote:
Op Mon, 09 Nov 2015 20:28:13 +0100 schreef Karl Heinz Marbaise
<[email protected]>:
Hi Robert,
On 11/9/15 5:57 PM, Robert Scholte wrote:
Hi Karl-Heinz,
properties for arrays? How would that work?
mvn org.apache.maven.plugins:maven-source-plugin:3.0.0-SNAPSHOT:jar
-Dmaven.source.includes='**/Test*.java','**/Life*.java'
...debug output:
......... (f) forceCreation = false
[DEBUG] (f) includePom = false
[DEBUG] (f) includes = [**/Test*.java, **/Life*.java]
This is not what I expected. Sorry for not testing,
no need to apologize..
> but does this work
for all Maven versions?
Hm... good question...not tested yet...
checked with Maven 3.0.5, 3.1.1, 3.2.5, 3.3.3 looks good...
And can you escape the single quote?
you mean like this:
mvn org.apache.maven.plugins:maven-source-plugin:3.0.0-SNAPSHOT:jar
-Dmaven.source.includes=\'**/Test*.java\',\'**/Life*.java\'
?
I know...but if you think this in consequence you should never add any
kind of properties...for usage on command line...
But i understand your point....
So the real question is which of those parameters should never being
changed on the command line ?
Was there a (valid) request to expose these parameters as property, or
was it done because these parameters didn't had a property yet?
I have done it cause the parameters didn't had a property yet...
Kind regards
Karl Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
