www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] Commented: (INFRA-881) Generated Docs have inconsistent line endings on Windows
Date Thu, 15 Mar 2007 01:19:09 GMT

    [ https://issues.apache.org/jira/browse/INFRA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480994

Sebb commented on INFRA-881:

If the svn:eol-style is missing, then it's best to fix this on the OS that matches the current
state of the file, otherwise lots of spurious updates are generated. This may mean applying
fixes on Windows and Unix. But it only has to be done once.

However, the eol-style may not be the only cause of spurious changes to generated html files
- it seems that the XSLT processors in some versions of Java generate additional  spaces.
I fixed this in the Jakarta build script some while back; yes it does take a bit longer to
remove the spaces, but it sure makes the SVN diff e-mails easier to read - indeed it eliminates
a lot of them.

> Generated Docs have inconsistent line endings on Windows
> --------------------------------------------------------
>                 Key: INFRA-881
>                 URL: https://issues.apache.org/jira/browse/INFRA-881
>             Project: Infrastructure
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: Website
>         Environment: Windows XP
>            Reporter: Niall Pemberton
>            Priority: Minor
>         Attachments: infra-site-build-wineol.patch
> Running the ant build [1] to generate the Apache Website in a Windows environment causes
documents with mixed line endings (i.e. both CRLF and LF) to be generated. Trying to commit
changes causes subversion to reject it with a message indicating this.
> This can be resolved using ant's fixcrlf task [2]:
>              <fixcrlf srcdir="${docs.dest}" includes="**/*.html"/>
> The only problem with adding the above step is with any documents without the "svn:eol-style"
property set to "native" - there were a few which I have just changed. I would commit this
myself, except for fear of screwing things up.
> [1] http://svn.apache.org/repos/asf/infrastructure/site/trunk/build.xml
> [2] http://ant.apache.org/manual/CoreTasks/fixcrlf.html

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message