Jörg Hohwiller created MANTRUN-243:
--------------------------------------

             Summary: regression: maven 4: 
                 Key: MANTRUN-243
                 URL: https://issues.apache.org/jira/browse/MANTRUN-243
             Project: Maven Antrun Plugin
          Issue Type: Bug
         Environment: maven 4.0.0-rc-1
maven-antrun-plugin 3.1.0
            Reporter: Jörg Hohwiller


I tested maven-antrun-plugin in latest 3.1.0 version with maven 4.0.0-rc-1 and 
it breaks the build while it is working with maven 3.9.9:
{code:java}
[INFO] BUILD FAILURE
[INFO] 
----------------------------------------------------------------------------------------------------------------
[INFO] Total time:  2.304 s
[INFO] Finished at: 2024-12-20T11:49:08+01:00
[INFO] 
----------------------------------------------------------------------------------------------------------------
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-antrun-plugin:3.1.0:run (pre-process-asciidoc) 
on project ide-doc: An Ant BuildException has occured: The following error 
occurred while executing this line:
[ERROR] 
D:\projects\IDEasy\workspaces\main\IDEasy\documentation\target\antrun\build-main.xml:23:
 javax.script.ScriptException: Sourced file: inline evaluation of: ``String 
path = project.getProperty("file_path").replace("\", "/");
      . . . '' Token Parsing Error: Lexical error at line 1, column 66.  
Encountered: "\n" (10), after : "\");": <at unknown location>
[ERROR]  in <unknown file>
[ERROR] around Ant part ...<for param="asciidoc-file">... @ 5:32 in 
D:\projects\IDEasy\workspaces\main\IDEasy\documentation\target\antrun\build-main.xml
 {code}
Source to the problem:

[https://github.com/devonfw/docgen/blob/3ba4dcc665d38c1daf4b89685ecc91a830ee7e05/pom.xml#L174]

Maybe there is a general backslash escaping bug in Maven 4.x that needs to be 
fixed. See also [https://github.com/groovy/gmaven/issues/34] what seems 
related, but may also be coincidence.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to