bvfalcon opened a new pull request, #135: URL: https://github.com/apache/maven-invoker-plugin/pull/135
In Addition to MINVOKER-140: exclude patterns works only if one or more include pattern(s) exists. This is a feature of [plexus-utils Component DirectoryScanner](https://github.com/codehaus-plexus/plexus-utils/blob/3896620b4fbf031b1b02b4d46b328c5839a231da/src/main/java/org/codehaus/plexus/util/DirectoryScanner.java#L447-L449). So, in our case command line parameter <code>-Dinvoker.test=!testX</code> (and configuration parameter [invokerTest](https://maven.apache.org/plugins/maven-invoker-plugin/run-mojo.html#invokerTest) ) works absolutely different way: **all projects** (not only testX) will be skipped. We must use <code>-Dinvoker.test=\*,!testX</code> or <code>-Dinvoker.test=!testX,\*</code> as workarround. In this commit I add forced additional include pattern "*" as default include patter for cases, if invoker.test contains only exclude-pattern. User still use <code>-Dinvoker.test=!testX</code> and all will work correctlz for him. The change has full back-compatibility with current plugin settings. Integration test invocation-cmdline-exclude is actualized. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
