V2.6.0

This release introduces now the "genmodeladdon nature" that must be enabled on the project so as to have the 'Generate Developer structure' displayed.

Also now can generate directly xtend code in the src folder.

What's Changed

• Generate either Java code or Xtend code for overridden classes by @PhilippeNoel in #93

Full Changelog: V2.4.0...v2.6.0

V2.3.0

Update version to 2.3.0

Signed-off-by: Olivier Prouvost <[email protected]>

v2.1.0

Fix these bugs :

Fix #74 : Names for Package and Factory in src are not named correctly in some cases
Fix #75 : Extended generic types not well generated
Fix #72 : The factory override extension is not generated
Fix #65 : Manage properly the target platform for photon
Fix #70 : In 2.0.0 the generated factory code becomes useless or could be simplified
Fix #71 : Name computation methods already defined in genModel classes

V2.0.0

This is the new release for genModelAddon.

One of the main changes is the usage of the current installed EMF templates to generate java code. No more templates copied in your project and dynamic templates used.

This is an important update that makes genModelAddon a professional tools for your code generation.

To use genModelAddon if you already used it with a previous version :

• in your genmodel remove the 'dynamic templates' property and the Template Directory that was set in the templates of your project.
• remove also the templates directory in your project.

V1.6.2

Fixes minor bugs and manage correctly generated emf extensions.

Fix #56 : generated package must be defined only once for the same model URI
Fix #55 : factory override must be defined only once for the same URI
Fix #54 : In eSet cast for enum are not managed
Fix #53 : package name's case must not be changed for dev generation
Fix #52 : Exception in getModelPath for my project
Fix #51 : The dev package and factory names should use the Prefix name to be computed !
Fix #50 : setRelevantValues should also set relevant values for 'src' patterns !
Fix #47 : Check the templates/model/Class.javajet
Fix #46 : project name is 'resource' when genmodel URI is 'platform:/resource/....'
Fix #43 : Remove trace during emf generation

V1.6.1

Fixes minor bugs, focus on windows tests and adds an oomph setup file.

V1.6.0

Basically this new release 1.6.0 fixes problems with generic EClass (like Folder), and manage correctly imports in src-gen files (it is not necessary to reorganize imports like before).

Fix issue #32 : Use now Java 8
Fix issue #20 : The generics types are not managed
Fix issue #39 : display file list not sorted
Fix issue #42 : The menu for genModelAddon is now empty
Fix issue #41 : Generic classes are not well generated in factory
Fix issue #44 : Multiple generics are not well generated
Fix issue #34 : Type returned by composition with single cardinality
Fix issue #33 : Dev implementation failed when the EClass is declared as
Fix issue #28 : Paths in Ant files
Fix issue #43 : Remove trace during emf generation
Fix issue #19 : Should call organize import or generate the correct

A new version with some fixes

This release (1.5.0) manages also the developer types for the EOperations. Some UI enhancements have been done too, to help the developer to change the names patterns in the launch dialog.

These bugs are fixed :

Fix issue #24: dialog is now resizable
Fix Issue #25 : add box to fix relevant values in genmodel
Fix issue #31 : change developper to developer
Fix Issue #29 : add copyright generation (and unit test)
Fix issue #30 : Operations parameters or return types are now generated

A better version ...

After the inheritance management, some cool bugs have been fixed :

• Fix Issue #17 : Should store the generation values in the properties (detail / githubweb)
• Fix issue#18 : genModel should automatically be set with dynamic (detail / githubweb)
• Fix issue #7 : The src dev directory should be considered as a src (detail / githubweb)

Now manage the inheritance in model

This release fixes mainly the issue #13. There was a problem when there was inheritance in the model.

For instance if we have in the model : B extends A (A <--- B) and the following namings M{0} and M{0}Impl for model generation and Dev{0}Interface and Dev{0}Impl for the developper structure, we had before (with version 1.0.0) :

• for interfaces : MA <--- DevAInterface and MA <--- MB <--- DevBInterface
• for implementations : MA <-- DevAImpl and MB <---- DevBImpl

With this new version we have the correct inheritance :

• for interfaces : MA <--- DevAInterface <--- MB <-- DevBInterface
• for implementation : MA <--- MAImpl <-- DevAImpl <---- MBImpl <--- DevBImpl

To make it working manuel steps must be proceeded :
This issue is fixed now with the following process :

• select dynamic templates in the genmodel
• set the templates directory to : 'yourProjectName'/templates in the genmodel
• generate the dev structure (it will create a specific Class.javajet files in the templates directory)
• generate again the model structure
• right click on the src-gen and organize imports.

It will be simplified later.

Thanks to tcharl (https://github.com/Tcharl) for its initial contribution.