[
https://issues.apache.org/jira/browse/MJAVADOC-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884133#comment-17884133
]
ASF GitHub Bot commented on MJAVADOC-811:
-----------------------------------------
michael-o opened a new pull request, #321:
URL: https://github.com/apache/maven-javadoc-plugin/pull/321
…s not on drive C and AutoRun is configured
This closes #321
Following this checklist to help us incorporate your
contribution quickly and easily:
- [ ] Make sure there is a [JIRA
issue](https://issues.apache.org/jira/browse/MJAVADOC) filed
for the change (usually before you start working on it). Trivial
changes like typos do not
require a JIRA issue. Your pull request should address just this
issue, without
pulling in other changes.
- [ ] Each commit in the pull request should have a meaningful subject line
and body.
- [ ] Format the pull request title like `[MJAVADOC-XXX] - Fixes bug in
ApproximateQuantiles`,
where you replace `MJAVADOC-XXX` with the appropriate JIRA issue.
Best practice
is to use the JIRA issue title in the pull request title and in the
first line of the
commit message.
- [ ] Write a pull request description that is detailed enough to
understand what the pull request does, how, and why.
- [ ] Run `mvn clean verify -Prun-its` to make sure basic checks pass. A
more thorough check will
be performed on your pull request automatically.
If your pull request is about ~20 lines of code you don't need to sign an
[Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the [Apache License Version 2.0, January
2004](http://www.apache.org/licenses/LICENSE-2.0)
you have to acknowledge this by using the following check-box.
- [ ] I hereby declare this contribution to be licensed under the [Apache
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
- [ ] In any other case, please file an [Apache Individual Contributor
License Agreement](https://www.apache.org/licenses/icla.pdf).
> 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
> Assignee: Michael Osipov
> Priority: Major
> Fix For: 3.10.1
>
>
> 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)
