[
https://issues.apache.org/jira/browse/MJAVADOC-473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17957830#comment-17957830
]
Olivier Lamy commented on MJAVADOC-473:
---------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-javadoc-plugin#764|https://github.com/apache/maven-javadoc-plugin/issues/764].
> Plugin looking for mvn.bat instead of mvn.cmd
> ---------------------------------------------
>
> Key: MJAVADOC-473
> URL: https://issues.apache.org/jira/browse/MJAVADOC-473
> Project: Maven Javadoc Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Components: javadoc
> Affects Versions: 2.9.1
> Reporter: Gili
> Assignee: Guillaume Boué
> Priority: Major
> Fix For: 2.10.4
>
>
> I get the following error message:
> {code}
> --- maven-javadoc-plugin:2.9.1:jar (attach-javadocs) @ japicmp-test ---
> The goal 'org.apache.maven.plugins:maven-javadoc-plugin:2.9.1:javadoc' has
> not been previously called for the module:
> 'com.github.siom79.japicmp:japicmp-test-v2:jar:0.9.2-SNAPSHOT'. Trying to
> invoke it...
> MavenInvocationException: Error configuring command-line. Reason: Maven
> executable not found at: C:\Program Files\apache-maven-3.3.9\bin\mvn.bat
> Creating fake javadoc directory to prevent repeated invocations:
> C:\Users\Gili\Documents\japicmp-develop\japicmp-testbase\japicmp-test-v2\target\apidocs
> Error fetching link:
> C:\Users\Gili\Documents\japicmp-develop\japicmp-testbase\japicmp-test-v2\target\apidocs/package-list.
> Ignored it.
> Building jar:
> C:\Users\Gili\Documents\japicmp-develop\japicmp-testbase\japicmp-test\target\japicmp-test-0.9.2-SNAPSHOT-javadoc.jar
> {code}
> According to https://issues.apache.org/jira/browse/MRELEASE-914 Maven 3.3.1
> renamed mvn.bat to mvn.cmd.
> Please update the plugin accordingly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
