Bug 573754 - [launch] Run configurations: Line delimiters changing from Windows to Unix and vice versa (project and workspace settings ignored)
Summary: [launch] Run configurations: Line delimiters changing from Windows to Unix an...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.21   Edit
Hardware: PC Windows 10
: P3 normal with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-25 05:35 EDT by Reto Hoehener CLA
Modified: 2022-06-18 16:10 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Reto Hoehener CLA 2021-05-25 05:35:04 EDT
Eclipse on Linux writes launch configurations with Unix line endings, ignoring project specific and workspace line delimiter settings.

For shared launch configurations under version control, this leads to conflicts.

This is particularly problematic if launch configs are configured with an "Alternate JRE": Renaming the JRE in the workspace settings will cause every single launch config in the workspace to be modified. For us this means hundreds of files in dozens of projects. Reverting those modifications without reverting the real changes is very time consuming. And accidental commits lead to confusion, because developers don't understand why the files changed and the diff doesn't show any changes (if whitespace is ignored).

Playing with the settings on the JRE tab in the launch config dialog will also cause the file to be modified.

The best solution would be for Eclipse to keep the existing line delimiters in existing launch configs.

Second best option would be to honor the project specific settings for new file line delimiters (although these are not "new" files).

Third best option would be to honor the workspace settings for new file line delimiters (although these are not "new" files).