Bug 217709 - Extension Point org.eclipse.wst.jsdt.core.inferrenceSupport does not load its extensions
Summary: Extension Point org.eclipse.wst.jsdt.core.inferrenceSupport does not load its...
Status: RESOLVED FIXED
Alias: None
Product: JSDT
Classification: WebTools
Component: General (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: 3.0 M6   Edit
Assignee: Phil Berkland CLA
QA Contact: Phil Berkland CLA
URL:
Whiteboard:
Keywords: contributed
Depends on:
Blocks:
 
Reported: 2008-02-04 12:34 EST by Matthias Kempka CLA
Modified: 2010-03-03 11:18 EST (History)
0 users

See Also:

Attachments
Updated extension point schema (2.75 KB, text/plain)
2008-02-04 12:37 EST, Matthias Kempka CLA 		no flags Details
View All 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 Matthias Kempka CLA 2008-02-04 12:34:47 EST 
Build ID: CVS Head

Steps To Reproduce:
1. Contribute to org.eclipse.wst.jsdt.core.inferrenceSupport 
2. Notice that it's never loaded


More information:
The InferrenceManager.TAG_INFERENGINE still points to the old element name "inferenceManager", but should be "inferenceProvider"

I'm also attaching an updated extension point schema that tells users more detailled what the extension point expects.
Comment 1 Matthias Kempka CLA 2008-02-04 12:37:22 EST 
Created attachment 88798 [details]
Updated extension point schema

this makes the inferenceProvider's class attribute a required element that says that contributions must implement the org.eclipse.wst.jsdt.internal.infer.InferrenceProvider
Comment 2 Phil Berkland CLA 2008-02-06 11:09:19 EST 
I have fixed the name, but havent updated the schema yet.
We are still actively working on this extension point, and hope to have it relatively stable in the next week for the M5 milestone.  We will be doing refactoring so that the extension does not use internal classes.
Comment 3 Matthias Kempka CLA 2008-02-08 05:35:11 EST 
Not depending on internal classes would be a great thing. Right now I'm suffering from the method InferrenceProvider.applysTo(CompilationUnitDeclaration scriptFile);
which I have to implement as InferrenceProvider, but that forces me to use CompilationUnitDeclaration that is exported to plug-in org.eclipse.wst.jsdt.compiler.tool only.
Comment 4 Phil Berkland CLA 2008-03-26 11:54:08 EDT 
Applied patch to schema.