[jira] [Resolved] (UIMA-3127) Improve Javadoc html generation to have consistent line endings

["Marshall Schor (JIRA)" <de...@uima.apache.org>]

     [ https://issues.apache.org/jira/browse/UIMA-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marshall Schor resolved UIMA-3127.
----------------------------------

    Resolution: Fixed

The code to run this was put into the apache-release profile so it mostly doesn't run at all.  On apache-releases, it runs all all projects but exits without doing anything unless there's a directory .../target/site/apidocs, in which case it runs on all *.html files found within that directory.
                
> Improve Javadoc html generation to have consistent line endings
> ---------------------------------------------------------------
>
>                 Key: UIMA-3127
>                 URL: https://issues.apache.org/jira/browse/UIMA-3127
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Build, Packaging and Test
>    Affects Versions: parent-pom-6
>            Reporter: Marshall Schor
>            Priority: Minor
>             Fix For: parent-pom-7
>
>
> The current Javadoc generation results in Javadoc html files which have mixed eol style on Windows platform.  Most are the windows cr lf style, but many are just the lf style.  
> This used to make no difference; however, now, with the new method of using SVN commits to add these to the release spot, SVN fails when the file has mixed eol styles, and the (default) for new files being added for files of type ".html" is to add the svn property eol-style:native.
> The way this used to work was:  (1) files were generated, having mixed eol styles (on windows).  (2) After the vote passed, they were "uploaded" to people.a.o; the upload tool converted the cr lf to just lf upon upload.
> Add a build step after the javadoc generation which runs the ant fixcrlf task on the .html files.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira