[
https://issues.apache.org/jira/browse/MJAVADOC-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707534#comment-16707534
]
Thorsten Schöning commented on MJAVADOC-469:
--------------------------------------------
{quote}
And yes, when asking for a test to reproduce this issue and having no response
for a long time is a good reason to close it as incomplete[...]
{quote}
The ticket creator waited almost two years for any reaction of anyone.
{quote}
I would expect that for all file-related javadoc argument an equivalant plugin
parameter should be available[...]
{quote}
Have a look at my use-case reported above:
Axis 2 is using some custom doclet with some custom argument and that argument
is forwarded using the options file created by the plugin. How should this
use-case be handled? Should nobody use custom doclets with custom arguments and
instead add options to the Maven plugin? Or do all users of pom.xml like that
of Axis 2 fix the builds on their own, like I needed to do? Or is it the
responsibility of the Maven-plugin to provide correct option files, which it
currently doesn't for some cases?
https://github.com/wso2/wso2-axis2-transports/blob/master/modules/testkit/src/main/java/org/apache/axis2/transport/testkit/doclet/ResourceInfoDoclet.java#L121
> 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
> Assignee: Robert Scholte
> Priority: Major
>
> 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" in AbstractJavadocMojo.addCommandLineOptions() .
> [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
(v7.6.3#76005)
