You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Ilya Basin (JIRA)" <ji...@apache.org> on 2016/07/29 14:55:20 UTC
[jira] [Updated] (MJAVADOC-469) javadoc-plugin does not double
backslashes in argument file
[ https://issues.apache.org/jira/browse/MJAVADOC-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ilya Basin updated MJAVADOC-469:
--------------------------------
Description:
On Windows `generate-rest-docs` goal of `maven-jira-plugin` calls `maven-javadoc-plugin` with:
{code}additionalparam: -output "C:\path\to\target\classes\resourcedoc.xml"{code}
If this argument was passed to `javadoc.exe` directly, I'm pretty sure this would work. However, the javadoc plugin generates an argument file[1] named "options" and executes:
{code}javadoc.exe ... @options{code}
The file contains all arguments with unescaped backslashes, although javadoc command documentation[2] suggests:
{quote}If a filename contains embedded spaces, put the whole filename in double quotes, and double each backslash ("My Files\\Stuff.java"){quote}
javadoc plugin version "2.4" is hardcoded in jira plugin, but I see no related changes in "2.10.4".
[1]: https://maven.apache.org/plugins/maven-javadoc-plugin/
[2]: http://docs.oracle.com/javase/7/docs/technotes/tools/windows/javadoc.html#argumentfiles
was:
On Windows `generate-rest-docs` goal of `maven-jira-plugin` calls `maven-javadoc-plugin` with:
{code}additionalparam: -output "C:\path\to\target\classes\resourcedoc.xml"{code}
If this argument was passed to `javadoc.exe` directly, I'm pretty sure this would work. However, the javadoc plugin generates an argument file[1] named "options" and executes:
{code}javadoc.exe ... @options{code}
The file contains all arguments with unescaped backslashes, although javadoc command documentation[2] suggests:
{quote}If a filename contains embedded spaces, put the whole filename in double quotes, and double each backslash ("My Files\\Stuff.java"){quote}
[1]: https://maven.apache.org/plugins/maven-javadoc-plugin/
[2]: http://docs.oracle.com/javase/7/docs/technotes/tools/windows/javadoc.html#argumentfiles
> javadoc-plugin does not double backslashes in argument file
> -----------------------------------------------------------
>
> Key: MJAVADOC-469
> URL: https://issues.apache.org/jira/browse/MJAVADOC-469
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
> Affects Versions: 2.10.4
> Reporter: Ilya Basin
>
> On Windows `generate-rest-docs` goal of `maven-jira-plugin` calls `maven-javadoc-plugin` with:
> {code}additionalparam: -output "C:\path\to\target\classes\resourcedoc.xml"{code}
> If this argument was passed to `javadoc.exe` directly, I'm pretty sure this would work. However, the javadoc plugin generates an argument file[1] named "options" and executes:
> {code}javadoc.exe ... @options{code}
> The file contains all arguments with unescaped backslashes, although javadoc command documentation[2] suggests:
> {quote}If a filename contains embedded spaces, put the whole filename in double quotes, and double each backslash ("My Files\\Stuff.java"){quote}
> javadoc plugin version "2.4" is hardcoded in jira plugin, but I see no related changes in "2.10.4".
> [1]: https://maven.apache.org/plugins/maven-javadoc-plugin/
> [2]: http://docs.oracle.com/javase/7/docs/technotes/tools/windows/javadoc.html#argumentfiles
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)