Bug 551441 - Base binding APIs should be improved to eliminate the use of raw types
Summary: Base binding APIs should be improved to eliminate the use of raw types
Status: NEW
Alias: None
Product: EMF
Classification: Modeling
Component: Edit (show other bugs)
Version: 2.20.0   Edit
Hardware: PC Mac OS X
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Ed Merks CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-25 03:24 EDT by Marcus Höpfner CLA
Modified: 2021-07-16 03:02 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 Marcus Höpfner CLA 2019-09-25 03:24:08 EDT 
The jface databinding APIs are now typed.
The EMF parts of the databinding are not typed yet, which still leads to warnings in the code.
Comment 1 Ed Merks CLA 2019-09-25 03:45:38 EDT 
Yes, I know.  But EMF as a whole is still compatible with Helios and we actually run builds to test that compatibility. 

At some point in the future, we (mostly I) will need to revisit that.  But at this point, a broad range of compatibility ensures the largest possible consumer base.
Comment 2 Marcus Höpfner CLA 2021-07-13 03:31:49 EDT 
(In reply to Ed Merks from comment #1)
> Yes, I know.  But EMF as a whole is still compatible with Helios and we
> actually run builds to test that compatibility. 
> 
> At some point in the future, we (mostly I) will need to revisit that.  But
> at this point, a broad range of compatibility ensures the largest possible
> consumer base.

Hi Ed,

is this still valid?
(I absolutely agree with the compatibility thing).
Comment 3 Ed Merks CLA 2021-07-16 03:02:29 EDT 
I still do builds like this:

https://ci.eclipse.org/emf/job/all-target-platforms/

So it's still a problem to use newer APIs and be backwards compatible...