[
https://jira.codehaus.org/browse/MJAVADOC-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=347684#comment-347684
]
Herve Boutemy commented on MJAVADOC-373:
----------------------------------------
you mean Oracle's javadoc is not consistent with platform? should open an issue
at them.
Notice Maven uses Apache's svnpubsub, and we fix m-site-p inconsistencies
through
[m-scm-publish-p|http://maven.apache.org/plugins/maven-scm-publish-plugin/]:
see MSITE-121
so if javadoc has the same issue, we didn't notice
> Make generated Javadoc html files have consistent new line endings
> ------------------------------------------------------------------
>
> Key: MJAVADOC-373
> URL: https://jira.codehaus.org/browse/MJAVADOC-373
> Project: Maven Javadoc Plugin
> Issue Type: New Feature
> Affects Versions: 2.9.1
> Environment: Windows
> Reporter: Marshall Schor
>
> On Windows, running the plugin results in Javadoc html files being built
> which have both cr lf and lf style line endings. Now that Apache requires
> uploads for releases via SVN, and because the default for SVN for new files
> (if using the standard conventional Apache settings from
> http://apache.org/dev/svn-eol-style.txt ) adds the svn property
> eol-style:native, SVN throws an error and won't upload the files because it
> finds "mixed" end-of-line characters in the file.
> It would nice if there was a new option, which (if set) would cause something
> like Ant's fixcrlf to be run on the generated .html files after the Javadoc
> generation.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
