Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 175190 - Problems with "External Plug-in Libraries"
Summary: Problems with "External Plug-in Libraries"
Status: RESOLVED FIXED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.3 M7   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-22 15:47 EST by DJ Houghton CLA
Modified: 2007-03-26 17:51 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 DJ Houghton CLA 2007-02-22 15:47:47 EST
build i0220

- create plug-in project "aaa"
- open Plug-ins view
- select a plug-in from your target and add it to Java search
- note the "External Plug-in Libraries" project is created
- in the package explorer, delete the "aaa" project
- note the error on the "External Plug-in Libraries" project because it is missing required plug-in "aaa"
Comment 1 Chris Aniszczyk CLA 2007-02-22 15:49:29 EST
yargh, you know how I feel about that visible project Wassim...
Comment 2 Wassim Melhem CLA 2007-02-22 15:59:38 EST
>you know how I feel about that visible project Wassim...

Now you expect me to know how you feel? :)
Comment 3 DJ Houghton CLA 2007-02-22 16:08:46 EST
Are you guys auditioning for a Dr Phil episode? :-)
Comment 4 Wassim Melhem CLA 2007-02-22 16:18:20 EST
DJ, for the past week or so, Chris has been creating a schism in the PDE family and I don't know what to do about that.  Help!
Comment 5 DJ Houghton CLA 2007-02-22 16:38:39 EST
Tsk tsk...isn't the PDE motto: "Build bridges, not schisms."?
Comment 6 Wassim Melhem CLA 2007-02-22 16:46:40 EST
yes, thanks DJ for being the voice of reason, once again.

"We Do Tooling but Our Business is People" - Wassim Melhem
Comment 7 Brian Bauman CLA 2007-02-22 16:58:06 EST
On a more technical note, why do we have workspace projects on the buildpath of our external java search project?  The JDT already keeps track of their source since they are projects, and the only thing in the java search project should be binary jars who should not need references to code in projects.
Comment 8 Wassim Melhem CLA 2007-02-22 17:08:50 EST
good question.

JDT does some "optimizations" when opening type hierarchies.  The External Libraries project cannot be standalone.  It must reference other plug-in projects in the workspace for type hierarchies to be created correctly.

Incidentally, that is why the Extrenal Libraries project has a JRE entry, even though it does not need it.  In its absence, java.lang.Object cannot be found on the project's classpath and no type hierarchy can ever created as a result.
Comment 9 Chris Aniszczyk CLA 2007-02-23 10:27:37 EST
We need to update our web page and EclipseCon slides to add that motto.

"We Do Tooling but Our Business is People" ;)
Comment 10 Wassim Melhem CLA 2007-02-24 21:56:01 EST
Fixed.
Comment 11 DJ Houghton CLA 2007-03-20 08:56:40 EDT
This is still a problem for me in build i0320-0010.

- I have the Core Tools project in my dev (in an extension location).
- I also have fragments/bundles which depend on it in my dev.
- I also have it in my workspace.
- When I delete it from my workspace, I get the errors.
Comment 12 Wassim Melhem CLA 2007-03-26 17:51:02 EDT
Fixed.