Download
Getting Started
Members
Projects
Community
Marketplace
Events
Planet Eclipse
Newsletter
Videos
Participate
Report a Bug
Forums
Mailing Lists
Wiki
IRC
How to Contribute
Working Groups
Automotive
Internet of Things
LocationTech
Long-Term Support
PolarSys
Science
OpenMDM
More
Community
Marketplace
Events
Planet Eclipse
Newsletter
Videos
Participate
Report a Bug
Forums
Mailing Lists
Wiki
IRC
How to Contribute
Working Groups
Automotive
Internet of Things
LocationTech
Long-Term Support
PolarSys
Science
OpenMDM
Toggle navigation
Bugzilla – Attachment #2549: org.eclipse.jdt.internal.ui.text.java.JavaCompletionProposal.startWith is now using InputMatcher.prefixEquals for
bug #26528
Home
|
New
|
Browse
|
Search
|
[?]
|
Reports
|
Requests
|
Log In
[x]
|
Terms of Use
|
Copyright Agent
View
|
Details
|
Raw Unified
| Return to
bug 26528
| Differences between
patch on org.eclipse.jdt.ui project
patch on org.eclipse.jdt.core project to provide input matcher extension point
org.eclipse.jdt.internal.codeassist.InputMatcher is responsable for managing the plugins which provide input matchers and combine the result.
eclipse\plugins\org.eclipse.jdt.core_2.1.0\plugin.xml adds <extension-point id="inputMatcher" name="%inputMatcher"/>
org.eclipse.jdt.internal.ui.text.java.JavaCompletionProposal.startWith is now using InputMatcher.prefixEquals
org.eclipse.jdt.internal.codeassist.CompletionEngine is using CharOperation.prefixEquals, Changed to InputMethod.prefixEquals
org.eclipse.jdt.internal.codeassist.InputMatcherPlugin is the interface that input matchers must implement. InputMatcher class delegates the call to the plugins.
and this patch
Collapse All
|
Expand All
Return to
bug 26528