[ https://issues.apache.org/jira/browse/MJAVADOC-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729191#comment-16729191 ]
Michael Osipov commented on MJAVADOC-469: ----------------------------------------- The funny thing is that the most recent Javadoc documentation does not even document the argument file behavior. It is completely unclear and opaque. This is for Java 8 .bq An argument file can include javac options and source file names in any combination. The arguments within a file can be space-separated or newline-separated. If a file name contains embedded spaces, then put the whole file name in double quotation marks. Java 11 says: Noting about this. Not even mention backslash or colon. Just made a quick test with 11, it still requires backslash escapes, sigh...what a mess. It does not require any escaping if you don't quite.. Oracle's lack of documentation is just frustrating. [~tschoening], your actual proposal is to unconditionally escape backslashes? > 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: Michael Osipov > 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)