Bug 386835 - GMF-T should generate code aligned with API deprecation status of Juno/Kelper
Summary: GMF-T should generate code aligned with API deprecation status of Juno/Kelper
Status: RESOLVED FIXED
Alias: None
Product: GMF-Tooling (ARCHIVED)
Classification: Modeling
Component: Generation / Templates (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P2 normal (vote)
Target Milestone: 3.1   Edit
Assignee: Michael Golubev CLA
QA Contact:
URL:
Whiteboard: Currency
Keywords: plan
Depends on: 380983
Blocks:
  Show dependency tree
 
Reported: 2012-08-08 09:39 EDT by Michael Golubev CLA
Modified: 2013-09-18 09:50 EDT (History)
1 user (show)

See Also:
borlander: kepler+

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 Michael Golubev CLA 2012-08-08 09:39:55 EDT 
In state of 3.0 release, GMFT generates the code which produces multiple warnings in standard Eclipse environment. 

It includes 
- still used raw JDK 1.4 types for collections
- usages of the deprecated or restricted APIs in the code 
- usages of the deprecated API in the plugin.xml's (e.g, GMFT still generates code for org.eclipse.ui.popupMenus extension point which may be removed in Kepler release)

According to bug #380983, templates in the GMF-T still take into account the possibility of the highly outdated JDK 1.4 which actually incapable of running the diagrams due to the required runtime environment of GMFT and its dependencies

During the Kepler release cycle most of these warnings in the generated code should be eliminated.
Comment 1 Michael Golubev CLA 2012-11-14 05:44:40 EST 
Moving to M4
Comment 2 Michael Golubev CLA 2013-09-18 09:50:29 EDT 
Delivered in 3.1