Bug 532562 - [content assist] Completes fully-qualified java.lang names in package-info.java
Summary: [content assist] Completes fully-qualified java.lang names in package-info.java
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 4.8   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-17 06:49 EDT by Andreas Sewe CLA
Modified: 2023-03-09 17:11 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 Andreas Sewe CLA 2018-03-17 06:49:58 EDT 
Noticed this while testing the Photon M6 Java EPP package.

To reproduce:

- Use the "New Java Package" wizard with "Create package-info.java" checked.
- In the generated package-info.java, add an "@" before the package keyword and trigger content assist:

  @<CTRL+SPACE>
  package org.example;

- Select the "Deprecated" proposal.
- This completes to the following:

  @java.lang.Deprecated
  package org.example;

Obviously, the java.lang qualification is unnecessary here.
Comment 1 Eclipse Genie CLA 2020-10-05 18:17:06 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 Jeff Johnston CLA 2020-10-05 18:29:14 EDT 
This still occurs for 4.18M1
Comment 3 Eclipse Genie CLA 2023-03-09 17:11:57 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.