Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 139307 - [registry] Missing Builders with partially qualified names
Summary: [registry] Missing Builders with partially qualified names
Status: RESOLVED DUPLICATE of bug 128866
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-runtime-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-28 16:43 EDT by brian fjeldstad CLA
Modified: 2006-05-01 06:40 EDT (History)
0 users

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 brian fjeldstad CLA 2006-04-28 16:43:23 EDT 
I have a plugin that was created for Eclipse 3.1.  It has 2 builders associated with a ProjectNature that worked for 3.1, 3.1.1, 3.1.2, & 3.2M1-M4.  As of 3.2M5 the builders started showing up in the Project Properties dialogs as "Missing builder (<fully qualified id>)".  This behaviour persists through 3.2RC1.

Has something changed in the Builder mechanism that is not backwards compatible?  Or is this a bug?
Comment 1 brian fjeldstad CLA 2006-04-28 17:09:17 EDT 
OK...I found the problem.  It seems that between 3.2M4 and 3.2M5 several extension points changed (I've noticed that org.eclipse.core.resources.markers & org.eclipse.core.resources.builders) and now require fully qualified path names.  

Is there somewhere where I can go to see what else "newly" requires fully qualified paths?
Comment 2 Thomas Watson CLA 2006-04-28 17:29:33 EDT 
This may be a dup of bug 128866.  Can you try M6?
Comment 3 brian fjeldstad CLA 2006-04-28 17:42:18 EDT 
It looks like a duplicate of that bug...not sure about M6, but, RC1 has the same problems.

Do I understand this right:

1.  if I leave the <?eclipse version="3.0"?>, I can maintain the same naming (unqualified id's with '.'s in them) I've always had (is this impacted at all by the version attribute in the plugin tag?).

2.  if I update to <?eclipse version="3.2"?>, I have to either change the ID's to remove the '.'s (thus breaking any premade projects' builds) or fully qualify the ID's in which case my plugin wouldn't work for any version of Eclipse prior to 3.2M5.
Comment 4 Pascal Rapicault CLA 2006-05-01 06:40:19 EDT 
Your understanding of the solution is correct.

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