db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5979) ant release target creates a release.properties that has conflicting line endings so automatic checkin fails
Date Wed, 03 Jul 2013 09:22:24 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13698777#comment-13698777
] 

ASF subversion and git services commented on DERBY-5979:
--------------------------------------------------------

Commit 1499287 from [~dyret]
[ https://svn.apache.org/r1499287 ]

DERBY-5979: Part a: Do not use \n to terminate lines in Apache License header String constant
and instead join the line strings with the value of line.separator property.
                
> ant release target creates a release.properties that has conflicting line endings so
automatic checkin fails
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5979
>                 URL: https://issues.apache.org/jira/browse/DERBY-5979
>             Project: Derby
>          Issue Type: Bug
>          Components: Build tools
>            Reporter: Kathey Marsden
>            Assignee: Dyre Tjeldvoll
>              Labels: derby_triage10_11
>         Attachments: derby-5979-1.diff, derby-5979-2.diff, derby-5979-3-a.diff, derby-5979-3-b.diff
>
>
> The ant release target  on Windows  creates release.properties with inconsistent line
endings that prevent checkin.
> This may be a configuration issue.  I have *.properties = svn:eol-style=native which
I think is correct but I could not diff or checkin the file until I removed the dos line endings.
 There are similar issues with the release notes but because they are not checked in as part
of the a script we document how to fix them up.

--
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

Mime
View raw message