Bug 380983 - [plan] Obsolete generation targeting JDK1.4, assume generics, annotations and for-each
Summary: [plan] Obsolete generation targeting JDK1.4, assume generics, annotations and...
Status: ASSIGNED
Alias: None
Product: GMF-Tooling (ARCHIVED)
Classification: Modeling
Component: Generation / Templates (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Michael Golubev CLA
QA Contact:
URL:
Whiteboard: Currency
Keywords: plan
Depends on:
Blocks: 386835
  Show dependency tree
 
Reported: 2012-05-30 00:52 EDT by Michael Golubev CLA
Modified: 2013-12-12 05:18 EST (History)
2 users (show)

See Also:
borlander: juno-


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Golubev CLA 2012-05-30 00:52:36 EDT
Actually GMFT templates contains a big deal of the code that tries to generate code compatible with pre-generics java (see CodeStyle.xpt). 

It makes difficult to read and maintain the templates, and also it does not solve any problems now, because generated code already depends on the external API only available for JDK 5+. 

Given that actual version of J2SE is 7, and that 1.4 is in EOL, we can safely obsolete generation for non-generics Java and simplify the templates.
Comment 1 Michael Golubev CLA 2012-05-30 00:53:36 EDT
We haven't done that for Juno, deferred to next release.
Comment 2 Michael Golubev CLA 2013-09-25 06:35:53 EDT
The code generated for Kepler already has most of the 1.4-stylish code eliminated,  from the generation except the places where the GMFT generated code calls old APIs that returns not-typed collections. 

As the platform itself and plugins GMF depends on (including APIs) are moving forward with adopting the modern Java code including the APIs, GMF-T shall ensure that at the end of Luna cycle the generated code does not produce warnings related to outdated code constructs. 

So I am now upgrading this bugzilla to be a plan item for Luna.