Bug 512401 - [ccp] Copy from clipboard to package explorer removes file header
Summary: [ccp] Copy from clipboard to package explorer removes file header
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 4.6   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-19 13:52 EST by Andrey Loskutov CLA
Modified: 2022-10-09 13:08 EDT (History)
1 user (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 Andrey Loskutov CLA 2017-02-19 13:52:12 EST 
Create a project with two packages, "a" and "b". Create file a.A as shown below:

/**
 * Copyright...
 */
package a;

public class A {
}

In the editor, select all and copy to clipboard Ctrl+A Ctrl+C.
Select package "b" in package explorer and use "Ctrl+V" to create b.A file: it will look like this:

package b;

public class A {
}

The problem is that the file header is removed by "fixing" the package name. I was hit by the bug by copying the code from git diff view to a different plugin in bug 320672...
Comment 1 Eclipse Genie CLA 2020-09-17 17:35:11 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.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2022-10-09 13:08:20 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.

--
The automated Eclipse Genie.