[jira] Commented: (TUSCANY-2019) SVN eol-style property not set correctly on all source files; other incorrect properties
[ https://issues.apache.org/jira/browse/TUSCANY-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12563781#action_12563781 ] Sebb commented on TUSCANY-2019: --- I've only concentrated on java and xml files; there are a lot of other text files that need to be checked. The other file types I've seen in SVN are: # type count # bpel6 # classpath 1 # componentType 114 # composite 316 # config 1 # constrainingType3 # css 8 # ctrl4 # dat 127 # doc 1 # emx 1 # ext 1 # fixme 1 # gif 2 # groovy 6 # handlers1 # jar 8 # jks 8 # jpg 9 # js 14 # jsp 6 # lck 1 # list2 # mar 1 # mf 79 # off 2 # pdf 2 # png69 # prefs 1 # project 4 # py 6 # rb 6 # scdl1 # schemas 1 # smd 2 # sql 3 # svg47 # tmp 1 # vm 11 # wsdl 90 # xq 4 # xsd 212 # xsdconfig 1 # xsl 2 Some of these are binary, e.g. jpg, gif, and probably doc. If you can confirm which are definitely text (and should have eol:native) I can generate more scripts. SVN eol-style property not set correctly on all source files; other incorrect properties Key: TUSCANY-2019 URL: https://issues.apache.org/jira/browse/TUSCANY-2019 Project: Tuscany Issue Type: Bug Reporter: Sebb Assignee: ant elder Attachments: addnative.txt, removeexexc.txt, svnjava.sh, svnxml.sh The SVN eol-style property needs to be set to native for .java, .xml and other text files, otherwise problems may arise when SVN is used from OSes with different line-endings. Note that the lists of files in the attachments are not exhaustive; I hope to add some more later -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-2019) SVN eol-style property not set correctly on all source files; other incorrect properties
[ https://issues.apache.org/jira/browse/TUSCANY-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12563778#action_12563778 ] Luciano Resende commented on TUSCANY-2019: -- Should we review and update the script we have under /etc and run that at least once before each release ? SVN eol-style property not set correctly on all source files; other incorrect properties Key: TUSCANY-2019 URL: https://issues.apache.org/jira/browse/TUSCANY-2019 Project: Tuscany Issue Type: Bug Reporter: Sebb Assignee: ant elder Attachments: addnative.txt, removeexexc.txt, svnjava.sh, svnxml.sh The SVN eol-style property needs to be set to native for .java, .xml and other text files, otherwise problems may arise when SVN is used from OSes with different line-endings. Note that the lists of files in the attachments are not exhaustive; I hope to add some more later -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-2019) SVN eol-style property not set correctly on all source files; other incorrect properties
[ https://issues.apache.org/jira/browse/TUSCANY-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12563788#action_12563788 ] Sebb commented on TUSCANY-2019: --- Re the script: http://svn.apache.org/repos/asf/incubator/tuscany/java/etc/set_svn_properties.sh It should not really be necessary if committers ensure that the correct SVN defaults are set up before adding any new files. However, it is useful as a backup. By the way, it might be sensible to drop the svn directories as follows: find . ! -path '*/.svn*' etc SVN eol-style property not set correctly on all source files; other incorrect properties Key: TUSCANY-2019 URL: https://issues.apache.org/jira/browse/TUSCANY-2019 Project: Tuscany Issue Type: Bug Reporter: Sebb Assignee: ant elder Attachments: addnative.txt, removeexexc.txt, svnjava.sh, svnxml.sh The SVN eol-style property needs to be set to native for .java, .xml and other text files, otherwise problems may arise when SVN is used from OSes with different line-endings. Note that the lists of files in the attachments are not exhaustive; I hope to add some more later -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-2019) SVN eol-style property not set correctly on all source files; other incorrect properties
[ https://issues.apache.org/jira/browse/TUSCANY-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12563191#action_12563191 ] Sebb commented on TUSCANY-2019: --- A few fixes for XML files: svn ps svn:eol-style native itest\exceptions-cross-binding\pom.xml svn ps svn:eol-style native itest\extended-api\pom.xml svn ps svn:eol-style native itest\exceptions-cross-binding-ws\pom.xml svn pd svn:executable modules\databinding-jaxb\pom.xml svn pd svn:executable modules\binding-ws-axis2\src\main\resources\org\apache\tuscany\sca\binding\ws\axis2\engine\config\axis2.xml svn pd svn:executable modules\binding-ws-axis2\pom.xml svn pd svn:executable modules\databinding-sdo\pom.xml svn pd svn:executable modules\databinding-axiom\src\test\resources\ipo.xml svn pd svn:executable modules\databinding-axiom\pom.xml svn pd svn:executable modules\binding-rmi\pom.xml svn ps svn:eol-style native modules\binding-jms\pom.xml SVN eol-style property not set correctly on all source files; other incorrect properties Key: TUSCANY-2019 URL: https://issues.apache.org/jira/browse/TUSCANY-2019 Project: Tuscany Issue Type: Bug Reporter: Sebb Attachments: addnative.txt, removeexexc.txt The SVN eol-style property needs to be set to native for .java, .xml and other text files, otherwise problems may arise when SVN is used from OSes with different line-endings. Note that the lists of files in the attachments are not exhaustive; I hope to add some more later -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
