[GROOVY-355] VerbatimGStringTest failures - Windows vs. Unix EOL problem

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.0-beta-5
• Fix Version/s: 1.0-beta-5
• Assignee: Unassigned
• Reporter: Rod Cope
• Created: 02/Apr/04 17:29
• Updated: 05/Dec/04 03:52
• Resolved: 03/Apr/04 21:03

Description

VerbatimGStringTest.groovy fails with latest CVS HEAD (4/2/04)

The test results contain "Expression: (string == Bob hey," followed by a UNIX EOL (0a) but contain "Values: string = Bob hey," followed by a Windows EOL (0d0a).

I checked the test case source and it contains a Windows EOL in the
heredoc and a "\n" in the assertion. So... it appears that somewhere along the line the GString is getting a UNIX EOL where there used to be a Windows EOL.