[jboss-jira] [JBoss JIRA] (WFLY-6695) JspTagTestCase fails on Windows

[Frank Langelage (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13250468#comment-13250468 ] 

Frank Langelage commented on WFLY-6695:
---------------------------------------

>From a plain DOS box the same result. Failure without my change, success with my chnange included.

I not got you completely I think.
git config --system -l
shows
core.autocrlf=true

git config --global -l
show nothing about crlf.

So the setting is as it should be, or not?
java and jsp files of this test on my harddisk have Dos\Windows line endings.


> JspTagTestCase fails on Windows
> -------------------------------
>
>                 Key: WFLY-6695
>                 URL: https://issues.jboss.org/browse/WFLY-6695
>             Project: WildFly
>          Issue Type: Bug
>          Components: Test Suite
>    Affects Versions: 10.1.0.Final
>         Environment: Windows 10, Oracle JDK 1.8.0_92
>            Reporter: Frank Langelage
>
> build.bat clean install failed with
> -------------------------------------------------------------------------------
> Test set: org.jboss.as.test.integration.jsp.JspTagTestCase
> -------------------------------------------------------------------------------
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.768 sec <<< FAILURE! - in org.jboss.as.test.integration.jsp.JspTagTestCase
> test(org.jboss.as.test.integration.jsp.JspTagTestCase)  Time elapsed: 0.486 sec  <<< FAILURE!
> org.junit.ComparisonFailure: expected:<This is a header[
> <div>tag</div>
> Static content]
> > but was:<This is a header[
> <div>tag</div>
> Static content
> ]
> >
> 	at org.junit.Assert.assertEquals(Assert.java:115)
> 	at org.junit.Assert.assertEquals(Assert.java:144)
> 	at org.jboss.as.test.integration.jsp.JspTagTestCase.test(JspTagTestCase.java:67)
> Replacing all occurence of "\n" with System.getProperty("line.separator") in the expected String solved the problem for me.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)