Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 347109 - Injecting both TypeConformanceComputer and XbaseTypeConformanceComputer
Summary: Injecting both TypeConformanceComputer and XbaseTypeConformanceComputer
Status: CLOSED FIXED
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: 2.0.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: RC2   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-25 02:40 EDT by Esa Ryhänen CLA
Modified: 2017-10-31 11:19 EDT (History)
2 users (show)

See Also:
sebastian.zarnekow: juno+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Esa Ryhänen CLA 2011-05-25 02:40:03 EDT
Build Identifier:  M20110210-1200

Xbase classes gets TypeConformanceComputer injected in some cases, and in other cases XbaseTypeConformanceComputer gets injected. For example XbaseJavaValidator gets TypeConformanceComputer injected, and FeatureCallChecker gets XbaseTypeConformanceComputer injected.

This requires binding a custom type conformance computer to both XbaseTypeConformanceComputer and TypeConformanceComputer when one binding should be enough.



Reproducible: Always
Comment 1 Sebastian Zarnekow CLA 2012-03-07 11:11:52 EST
We should make sure that we do not stumble accross this one.
Comment 2 Sebastian Zarnekow CLA 2012-04-02 16:39:30 EDT
Fixed another case where we injected the XbaseTypeConformanceComputer. Solution for comment #1 still pending.
Comment 3 Sven Efftinge CLA 2012-05-29 03:41:46 EDT
I checked the current code base. There are no references to XbaseTypeConformanceComputer other than bindings and tests.
Comment 4 Eclipse Webmaster CLA 2017-10-31 11:07:55 EDT
Requested via bug 522520.

-M.
Comment 5 Eclipse Webmaster CLA 2017-10-31 11:19:25 EDT
Requested via bug 522520.

-M.