[MJAVADOC-811] javadoc.bat fails to execute on Windows when project is not on drive C and AutoRun is configured

[jira-importer]

Sebastian T opened MJAVADOC-811 and commented

Trying to execute the javadoc plugin in a Maven build on Windows results in

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.8.0:jar (attach-javadocs) on project myproject: MavenReportException: Error while generating Javadoc:
[ERROR] Exit code: 1 - javadoc: error - cannot read options (The system cannot find the file specified)
[ERROR]
[ERROR] Command line was: cmd.exe /X /C "F:\java\temurin_jdk11\bin\javadoc.exe @options @packages"[ERROR]
[ERROR] Refer to the generated Javadoc files in 'F:\projects\myproject\target\apidocs' dir. 

when the project is not on the system drive and HKEY_CURRENT_USER\Software\Microsoft\Command Processor\AutoRun is configured to some directory on drive C. Then cmd.exe will not execute in the current directory but in the directory specified via AutoRun. This is the case in a corporate environment I am working in.

The solution is trivial by adding the /D flag to cmd.exe

---

Affects: 3.8.0

Issue Links:

• MJAVADOC-671 Generated javadoc.bat fails to execute in Windows10

Remote Links:

• GitHub Pull Request #321
  

[jira-importer]

Michael Osipov commented

sjaranowski, I have this Plexus crap running a wrapping around processes.

[jira-importer]

Sebastian T commented

I opened a PR against plexus-utils to address this. codehaus-plexus/plexus-utils#272

[jira-importer]

Michael Osipov commented

I will take care of the PU PR and same for Maven Shared Utils.

[jira-importer]

Michael Osipov commented

Can't release anything for Codehaus Plexus, need someone else to push the new release.

[jira-importer]

Michael Osipov commented

Sebastian T, branch created, please test.

[jira-importer]

Michael Osipov commented

Fixed with db6d7f6ec355dd26c7f4841ad2c63ff4df456422.