Bug 496186 - [launch] Launch config editor rewrites line breaks in encoded VM arguments string
Summary: [launch] Launch config editor rewrites line breaks in encoded VM arguments st...
Status: REOPENED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.5.2   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2016-06-15 10:48 EDT by Tobias Oberlies CLA
Modified: 2020-06-04 04:07 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 Tobias Oberlies CLA 2016-06-15 10:48:57 EDT 
In our team, we have checked-in launch configurations. To improve the readability of the VM arguments, we separated them with line breaks. On a Mac, this is persisted in the following way in the .launch file:

<stringAttribute key="org.eclipse.jdt.launching.VM_ARGUMENTS" value="-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog&#10;-Dorg.apache.commons.logging.simplelog.showdatetime=true&#10;-Dorg.apache.commons.logging.simplelog.log.org.apache.http.wire=DEBUG"/>

However when I open this launch configuration on Windows, it becomes dirty as soon as I switch to the Arguments tab. If I save it, the VM_ARGUMENTS line is changed to

<stringAttribute key="org.eclipse.jdt.launching.VM_ARGUMENTS" value="-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog&#13;&#10;-Dorg.apache.commons.logging.simplelog.showdatetime=true&#13;&#10;-Dorg.apache.commons.logging.simplelog.log.org.apache.http.wire=DEBUG"/>

This is quite annoying. It effectively means that such a file can no longer be shared in a team.
Comment 1 Eclipse Genie CLA 2020-05-28 19:48:41 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Simon Lieschke CLA 2020-06-03 14:44:11 EDT 
This is still an issue with Eclipse 4.5.0.

This along with similar behaviour in Bug 404210 makes it frustrating to share launch configurations between Windows and non-Windows users.
Comment 3 Sarika Sinha CLA 2020-06-04 01:50:54 EDT 
@Paul,
Will you be interested to work on this?
Comment 4 Paul Pazderski CLA 2020-06-04 04:07:37 EDT 
I had looked into this a bit as it come up as staled but either could not reproduce it or directly find a reason for the failure. (forgot what of the two it was)

But I can take a second look.