Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 205457

Summary: Spurious "unknown extension point" message for user-defined extension points
Product: [Eclipse Project] PDE Reporter: Robert M. Fuhrer <rfuhrer>
Component: UIAssignee: PDE-UI-Inbox <pde-ui-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: aniefer, baumanbr, jurgen.vinju, markus.kell.r, mohseni, pwebster
Version: 3.2.2   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard: stalebug
Attachments:
Description Flags
A pair of projects that exhibit the "unknown extension point" bug none

Description Robert M. Fuhrer CLA 2007-10-04 11:55:44 EDT 
The plugin compiler claims that a user-defined extension point is unknown when processing an extension of that extension point. There need be no Java classes involved (e.g. a "pure metadata" extension point exhibits the problem), and the extension point schema seems not to matter.

We originally saw the problem in a workspace of ~20 plugins, and all of the extension points we defined had the same problem. We boiled it down to the following trivial scenario:

  Plugin A                      Plugin B (depends on A)
  -------------------------     --------------------------
  | Extension Point EPa   |     |  Extension Eb of EPa   |
  -------------------------     --------------------------

The PDE compiler issues the error message "Unknown extension point A.EPa" and highlights the extension point ID in the extension definition in Plugin B's plugin.xml file.

Note that the PDE compiler seems to accept extensions of Eclipse platform-supplied extension points without problems.

The above scenario was constructed in a completely fresh, otherwise empty workspace using a fresh install of Eclipse 3.2.2.

The problem occurs under Eclipse 3.2.2 on Linux, but doesn't occur under Eclipse 3.2.2 on Windows using identical source pulled from a CVS repository, nor does it occur under Eclipse 3.3 on Linux.

I'll attach a zip file with two tiny projects that demonstrate the problem.
Comment 1 Robert M. Fuhrer CLA 2007-10-04 11:59:54 EDT 
Created attachment 79741 [details]
A pair of projects that exhibit the "unknown extension point" bug
Comment 2 Brian Bauman CLA 2007-10-04 16:52:30 EDT 
Hi Robert,

Is there any more details you can give me about your environment?

On Red Hat Enterprise 4, I downloaded 3.2.2, started a new workspace (ran using IBM JRE 5.0), imported the projects, and did not see any problems...
Comment 3 Brian Bauman CLA 2007-10-04 17:02:36 EDT 
Note, this could be a dup of bug 182054.  For right now I want to keep this open in case we can reproduce this bug.  Note 182054 also mentions recent builds where this seems to not be a problem after 3.3.
Comment 4 Jurgen J. Vinju CLA 2007-10-05 10:22:11 EDT 
This happened on a T41p Thinkpad with Ubuntu Feisty Fawn installed.

The JVM is ibm-java2-i386-50, java -version:
java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition (build pxi32devifx-20070806 (SR5a))
IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Linux x86-32 j9vmxi3223-20070426 (JIT enabled)
J9VM - 20070420_12448_lHdSMR
JIT  - 20070419_1806_r8
GC   - 200704_19)
JCL  - 20070725

It happened with both the Ubuntu version of Eclipse 3.2.2 and the normal Eclipse 3.2.2 from eclipse.org. We started with the Ubuntu version however, and continued with the eclipse.org 3.2.2. on the same workspace.
Comment 5 Brian Bauman CLA 2007-10-05 16:47:11 EDT 
(In reply to comment #4)

> It happened with both the Ubuntu version of Eclipse 3.2.2 and the normal
> Eclipse 3.2.2 from eclipse.org. We started with the Ubuntu version however, and
> continued with the eclipse.org 3.2.2. on the same workspace.

Can you reproduce the problem with 3.2.2 from eclipse.org on a new workspace?  I am not familiar with FiestyFawn and want to make sure it is not causing the problem.
Comment 6 Jurgen J. Vinju CLA 2007-10-05 17:24:59 EDT 
That was a good call. I reinstalled the Ubuntu 3.2.2 version, it does have the bug. The eclipse.org 3.2.2 version does NOT have the bug. 

I verified this by opening the workspace with the different versions in different orders (create it with one, open it with the other, and vice versa). Only the Ubuntu version triggers the bug and always triggers the bug.
Comment 7 Eclipse Genie CLA 2019-07-03 18:05:13 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.