[
https://issues.apache.org/jira/browse/SUREFIRE-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14620856#comment-14620856
]
Tibor Digana commented on SUREFIRE-1166:
----------------------------------------
[~matthias.gradl]
I am open for multiple commits in one PR on GitHub. Feel free to update Javadoc
in AbstractSurefireMojo.java#test,
maven-surefire-plugin/src/site/apt/examples/inclusion-exclusion.apt.vm, and
maven-surefire-plugin/src/site/apt/examples/single-test.apt.vm.
> Include/Exclude regex pattern for a path is incorrectly replaced on Windows
> ---------------------------------------------------------------------------
>
> Key: SUREFIRE-1166
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1166
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin
> Affects Versions: 2.18.1
> Environment: Windows
> Reporter: Matthias Gradl
>
> On non-unix systems, the file scanner converts slashes ("/") into the
> file-system appropriate separator (eg. "\" on Windows) thus colliding with
> the standard escape character in regex Strings.
> For regex pattern matching a path (segment) to a test package (like:
> "%regex[.*/smoketest/.*Test\.java]" this leads to unusable patterns:
> "%regex[.*\smoketest\.*Test\.java]"
> There needs to be a more sophisticated replacement happening when the include
> string is actually a regex pattern.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
