Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 352523 - Introducing a new dependency is too cumbersome
Summary: Introducing a new dependency is too cumbersome
Status: CLOSED DUPLICATE of bug 237638
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-19 22:55 EDT by Sahoo CLA
Modified: 2011-07-20 09:06 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 Sahoo CLA 2011-07-19 22:55:20 EDT
In a Plugin project when I reference a new type in code, the Java editor shows me an option to fix the project set up to reference additional library containing the type in build path. e.g., try doing the following:
Create a new Plugin project.
Chose the BundleActivator class created by the wizard.
Introduce a variable called "LogService logService" or some other type which is not already visible to the plugin.

You shall see editor unable to resolve the type, but in the list of quick fix options, you shall an option to "fix project setup." Select that option and you shall be presented with a dialog asking to manually configure build path. I don't think that's the correct suggestion. The correct way to fix the issue should involve adding the appropriate package supplying the type to Import-Package using the manifest editor. More over, I expected the IDE to suggest me with the package that I need to add to my Import-Package to resolve the new type. It currently expects me to know that already or use some other technique to discover the bundle name. 

This issue was discussed in the forum thread:
http://www.eclipse.org/forums/index.php/t/221813/
Comment 1 Curtis Windatt CLA 2011-07-20 09:06:23 EDT

*** This bug has been marked as a duplicate of bug 237638 ***