Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 327100

Summary:	enhance Team->File Content preference page
Product:	[Eclipse Project] Platform	Reporter:	Sven Köhler <sven.koehler>
Component:	Runtime	Assignee:	platform-runtime-inbox <platform-runtime-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	tomasz.zarna
Version:	3.6.1
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:	stalebug
Bug Depends on:
Bug Blocks:	271778

Description Sven Köhler

2010-10-06 08:43:23 EDT

Build Identifier: 

It seems to me, that the current Team->File Content preference page has been designed with the needs of SVN in mind. Per file pattern, one can only select between binary and ascii.

SVN distinguishes between 5 options:
binary file (svn:mime-type is set to application/*)
ascii files with native line ending (svn:eol-style is set to native)
ascii files with CRLF line ending (svn:eol-style is set to CRLF)
ascii files with LF line ending (svn:eol-style is set to LF)
ascii files with CR line ending (svn:eol-style is set to CR)


The Team->File Content preference page should be enhanced, such that the page provides all information needed for SVN plugins. Furthermore, the Eclipse Text Editor can profit from this. For example, if *.bat is set to CRLF in that list, the Eclipse editor could save *.bat with CRLF line endings by default (of course, if the file is added to SVN, the Editor should use the settings provided by the SVN plugin).

Reproducible: Always

Comment 1 Tomasz Zarna

2010-10-07 06:37:07 EDT

Sven, what you said makes sense to me, but I think you should first talk to Platform/Runtime guys. They keep track of the line separator preference. Currently, you can set the preference on a project level and all new files will be created keeping that in mind, but afaik there is no way to set/get the preference for an individual file.

Moving to Runtime to comment. Feel free to bounce back if you think Team has all the tools to implement it.

Comment 2 Eclipse Webmaster

2019-09-06 15:37:13 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.

If you have further information on the current state of the bug, please add it. 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.

Comment 3 Eclipse Genie

2022-02-16 01:21:24 EST

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.