Bug 124924 - [api] LogicalPackage access needed (it is internal)
Summary: [api] LogicalPackage access needed (it is internal)
Status: RESOLVED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1.1   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: api
Depends on:
Blocks:
 
Reported: 2006-01-23 15:03 EST by Wynne Crisman CLA
Modified: 2010-08-11 10:55 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 Wynne Crisman CLA 2006-01-23 15:03:27 EST 
Selections in the package explorer fire selection events and pass the LogicalPackage as the selections for packages where classes come from multiple sources.  Since LogicalPackage is an internal class and there is no useful interface, plug-in developers are forced to use the internal LogicalPackage class.  Can we either make this class non-internal, or provide a non-internal interface?
Comment 1 Olivier Thomann CLA 2006-01-23 19:03:39 EST 
Move to JDT/UI
Comment 2 Martin Aeschlimann CLA 2006-01-24 05:34:59 EST 
Note it's not in the package explorer, just the packages view (Java browsing perspective). You're right, but we're hesitating. How urgent is this?
Comment 3 Wynne Crisman CLA 2006-01-24 20:12:28 EST 
LogicalPackage does currently provide access to all the references I need so it is not urgent.  It would just be nice not to reference internal class in Eclipse.
Comment 4 Dani Megert CLA 2010-08-11 10:55:23 EDT 
We won't make that API.