You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Sebastian T (Jira)" <ji...@apache.org> on 2024/09/18 16:16:00 UTC
[jira] [Updated] (MJAVADOC-811) javadoc.bat fails to execute on Windows when project is not on drive C and AutoRun is configured
[ https://issues.apache.org/jira/browse/MJAVADOC-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sebastian T updated MJAVADOC-811:
---------------------------------
Description:
Trying to execute the javadoc plugin in a Maven build on Windows results in
{noformat}
[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.
{noformat}
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
was:
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
> javadoc.bat fails to execute on Windows when project is not on drive C and AutoRun is configured
> ------------------------------------------------------------------------------------------------
>
> Key: MJAVADOC-811
> URL: https://issues.apache.org/jira/browse/MJAVADOC-811
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
> Affects Versions: 3.8.0
> Environment: Windows 10, Java 11, Maven 3.9.9
> Reporter: Sebastian T
> Priority: Major
>
> Trying to execute the javadoc plugin in a Maven build on Windows results in
> {noformat}
> [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.
> {noformat}
> 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
--
This message was sent by Atlassian Jira
(v8.20.10#820010)