You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Abel Salgado Romero (JIRA)" <ji...@apache.org> on 2017/09/25 11:50:00 UTC
[jira] [Created] (MINVOKER-226) run goal failing on Windows +
OracleJDK 8-144
Abel Salgado Romero created MINVOKER-226:
--------------------------------------------
Summary: run goal failing on Windows + OracleJDK 8-144
Key: MINVOKER-226
URL: https://issues.apache.org/jira/browse/MINVOKER-226
Project: Maven Invoker Plugin
Issue Type: Bug
Environment: Windows 7 and Windows 8.1 (2 different machines)
Oracle JDK 8-144
Maven 3.5.0
maven-invoker-plugin: from 2.0.0 to 3.0.1
Reporter: Abel Salgado Romero
Priority: Minor
Attachments: logs.txt
maven-invoker-plugin (version 2.0.0) run goal started failing on Windows 8.1 and Windows 7 with OracleJDK 8.144. It worked fine previously.
Runs OK on MacOS (JDK 8-133 and 8-144), and Ubuntu TraviCI and Windows AppVeyor.
Though the issue started with invoker 2.0.0, I am fine to focus on 3.0.1 since it's the current version. Also 2.0.0 and 3.0.0 show a different error.
With 3.0.1 everything seems to run fine but the validation scripts fail because they cannot find the generated files of the plugin being tested (see this branch https://github.com/abelsromero/asciidoctor-maven-plugin/tree/it_test_fail_on_Windows_jdk8_144).
That's true, the target directory does not hold the generated files but running with -X shows that the goals are apparently executed as seen by the line
{{[DEBUG] Executing: cmd.exe /X /C "I:\babun\.babun\cygwin\home\abelsr\.sdkman\candidates\maven\3.5.0\bin\mvn.cmd -B -X -D maven.repo.local=C:\Users\abelsr\.m2\repository -s C:\Users\abelsr\AppData\Local\Temp\invoker-settings4165519454880719356.xml clean asciidoctor:process-asciidoc"}}
Running the same command without the custom settings file in the it-tests directory works fine and generates the files.
NOTE: even if you see in the paths of the attached log that files are in a Babun home, I run the command {{mvn clean verify -Prun-its -X}} from a standard cmd shell.
Could it be, that the plugin runs the tests on another directory?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)