Bug 424352 - Launches ignore workspace line-endings preference
Summary: Launches ignore workspace line-endings preference
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.4   Edit
Hardware: All All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on: 424353
Blocks:
  Show dependency tree
 
Reported: 2013-12-18 11:47 EST by Ed Willink CLA
Modified: 2015-05-15 07:58 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ed Willink CLA 2013-12-18 11:47:36 EST 
Windows users often configure their workspaces to maximize Unix compatibility; workspace preference and project settings.

A JUnit launch should therefore (at least as an option) propagate the workspace line endings preference to the Java system property of the launch JVM.
Comment 1 Dani Megert CLA 2013-12-19 08:12:17 EST 

*** This bug has been marked as a duplicate of bug 269580 ***
Comment 2 Ed Willink CLA 2013-12-19 11:10:32 EST 
No. bug 269580 requests the launch configuration file to use Unix line endings.

This bug requests that the launched process have an environment in which the Java property has Unix line endings.
Comment 3 Dani Megert CLA 2014-01-13 09:36:10 EST 
(In reply to Ed Willink from comment #2)
> No. bug 269580 requests the launch configuration file to use Unix line
> endings.
> 
> This bug requests that the launched process have an environment in which the
> Java property has Unix line endings.

Sorry, you're right.


If I really wanted to maximize Unix compatibility, then I'd set the 'line.separator' property default VM argument in the JREs ('Installed JREs' preference page. However, this does not work (see bug 424353 comment 1).

I'm marking this as a duplicate of bug 424353, since that would solve this issue here and because there's no way to fix this bug here as outline in bug 424353 comment 1.

*** This bug has been marked as a duplicate of bug 424353 ***
Comment 4 Ed Willink CLA 2014-01-13 10:16:24 EST 
Bug 424353 is open again as helpwanted.
Comment 5 Dani Megert CLA 2014-01-13 10:43:27 EST 
(In reply to Dani Megert from comment #3)
> If I really wanted to maximize Unix compatibility, then I'd set the
> 'line.separator' property default VM argument in the JREs ('Installed JREs'
> preference page.

Would this not fix your use case? I'd assume this to be the safest thing if you really want max. Unix compatibility. And it would not only "fix" the JUnit case.
Comment 6 Ed Willink CLA 2014-01-13 11:27:53 EST 
(In reply to Dani Megert from comment #5)
> (In reply to Dani Megert from comment #3)
> > If I really wanted to maximize Unix compatibility, then I'd set the
> > 'line.separator' property default VM argument in the JREs ('Installed JREs'
> > preference page.
> 
> Would this not fix your use case? I'd assume this to be the safest thing if
> you really want max. Unix compatibility. And it would not only "fix" the
> JUnit case.

It's similar, but if I have three JVMs registered, I would have four settings
- Eclipse workspace
- 3 JVM settings
which I need to keep consistent, when all I really want is to say good bye to CR LF new lines forever.