[
https://issues.apache.org/jira/browse/PLUTO-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555598#action_12555598
]
Elliot Metsger commented on PLUTO-456:
--------------------------------------
Yes, you need to enable auto-props in your subversion config file and make sure
you have specified the filename patterns and svn:eol-style property. It also
helps to specify the mime type of the file.
Files that you 'svn add' will get these properties set on them automatically if
the file matches the pattern.
E.g. in ~/.subversion/config
....
enable-auto-props = yes
[auto-props]
*.java = svn:mime-type=text/plain;svn:eol-style=native;svn:keywords=Id
*.properties = svn:mime-type=text/plain;svn:eol-style=native
*.xml = svn:mime-type=text/xml;svn:eol-style=native
...
> fix line endings on files.
> --------------------------
>
> Key: PLUTO-456
> URL: https://issues.apache.org/jira/browse/PLUTO-456
> Project: Pluto
> Issue Type: Improvement
> Components: general
> Affects Versions: 1.1.4
> Reporter: Elliot Metsger
> Assignee: Elliot Metsger
> Priority: Minor
> Fix For: 1.2.0, 1.1.5, 1.1-286-trunk-merge
>
>
> Line endings are inconsistent on the java source files, and I suspect there
> are inconsistent line endings on other files as well in the pluto project.
> It's annoying, and also impedes patch application.
> I plan to update the line endings on text files ending with the following
> extensions, and then setting the svn property 'svn:eol-style' to "native" for
> those files.
> apt
> css
> dtd
> fml
> html
> inc
> js
> jsp
> properties
> tld
> txt
> xml
> xsd
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
