[MENFORCER-370] <condition/> should not take resolved properties as Java string, but escape backslashes

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 3.0.0-M2
• Component/s: Plugin

Environment

Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Java version: 11.0.9.1, vendor: ojdkbuild
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

• Assignee: Robert Scholte
• Reporter: Damian
• Created: 31/Dec/20 13:31
• Updated: 11/Jul/21 10:57
• Resolved: 11/Jul/21 10:57

Description

Running Maven with ${project.basedir} in the <evaluateBeanshell><condition> in a pom.xml fails under Windows, while Linux is fine.
Already

    <evaluateBeanshell>
        <condition>
            print(java.nio.file.Paths.get("${project.basedir}/".replace("\\", "/"));
            1==1
        </condition>
    </evaluateBeanshell>

fails with Couldn't evaluate condition... as ${project.basedir} is apparently taken as a Java string directly, w/o escaping the backslashes.
While the message part

    <evaluateBeanshell>
        <condition>
            1==0
        </condition>
        <message>condition failed, project.basedir=${project.basedir}</message>
    </evaluateBeanshell>

logs the Windows path correctly:

    [WARNING] Rule 2: org.apache.maven.plugins.enforcer.EvaluateBeanshell failed with message:
    condition failed, project.basedir=C:\Users\me\git\project\dir_with_pom_file