[
https://issues.apache.org/jira/browse/JENA-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian McBride updated JENA-409:
-------------------------------
Attachment: gitattributes.gitattributes
console.log.txt
Console log of test failure and gitattributes
> Test failures building on windows after GIT pull
> ------------------------------------------------
>
> Key: JENA-409
> URL: https://issues.apache.org/jira/browse/JENA-409
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ
> Environment: Windows8 GIT
> Reporter: Brian McBride
> Priority: Minor
> Attachments: console.log.txt, gitattributes.gitattributes
>
>
> On windows (8):
> Pull all branches from the GIT mirror
> Switch to trunk branch
> mvn clean install
> results in test failures.
> The tests that are failing are RIOT Turtle parser tests involving multiline
> literals. The input files are:
> jena-arq/testing/RIOT/Lang/Turtle/turtle-subm-15.ttl
> jena-arq/testing/RIOT/Lang/Turtle/turtle-subm-16.ttl
> jena-arq/testing/RIOT/Lang/TurtleSubm/test-17.ttl
> jena-arq/testing/RIOT/Lang/TurtleSubm/test-18.ttl
> The reason the tests are failing is that by default, GIT changes the line
> endings of text files to the platform default line endings on checkout.
> Therefore, on checking out from GIT, the LF characters within the multiline
> literals in these files are replaced by CR LF. When parsed the literals then
> do not match the expected results. They have unexpected CR characters in
> them.
> To fix this, I have created a .gitattributes file in the Jena root directory
> that tells GIT to use LF line endings for these four files.
> After checking this file in and then doing:
> git rm --cached -r .
> git reset --hard
> git add .
> git commit -m "Normalize line endings"
> then Jena builds fine. I would expect that if such a .gitattributes file
> were in the GIT repository when I did the pull, the build would just work out
> of the box, but I don't know that to be the case.
>
--
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
