Bug 542431 - [code mining] Formatting lost in target editor after clicking reload code mining annotation
Summary: [code mining] Formatting lost in target editor after clicking reload code min...
Status: NEW
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.10   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-05 07:46 EST by Noopur Gupta CLA
Modified: 2022-11-19 14:02 EST (History)
2 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 Noopur Gupta CLA 2018-12-05 07:46:52 EST 
I20181204-0600

- Consider a target file with source having the given formatting:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<?pde version="3.8"?>

<!-- my test target -->
<target name="t1">
	<locations>
		<location path="C:\Eclipse\Builds\eclipse-SDK-I20181204-0600\eclipse" type="Profile"/>
	</locations>
</target>

- Click "Reload Target Platform" code mining in the editor or the link from the Environment tab.

=> The formatting (newlines) are lost.
Comment 1 Noopur Gupta CLA 2018-12-05 07:51:09 EST 
This was working fine in Eclipse 4.9 (I20180906-0745).
Comment 2 Eclipse Genie CLA 2020-11-28 11:51:46 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.

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.

--
The automated Eclipse Genie.
Comment 3 Eclipse Genie CLA 2022-11-19 14:02:27 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.

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.

--
The automated Eclipse Genie.