History of Kermeta development

V1.1.0 (03/03/2008)

New features

• Improvement of the speed of the typechecker (x2).
• Addition of "Clean" and "Typecheck this file" button in the toolbar in order to help with some trouble of the typechecker.
• Improvement of UML MDK for profiles support.
• #4365; internal error should be reported into the error log
• #139; Implement "orElse" and "andThen". Partial support : the operations are available on boolean, but no dedicated surface syntax has been deployed yet.
• #1022; degraded editor response time when used for long time.
• #1759; Improving loading performances. (applies to the loading of kmt files)
• Please note that kermeta metamodel now use a nsURI that includes a version umber in order to improve version robustness. In this release the nsURI is "http://www.kermeta.org/kermeta/1_0_0//kermeta"

Bug fixed

• #311; Difference between kermeta::reflection and kermeta::language::structure
• #907; No line indication for a "no null" constraint violation
• #3327; loading files with dependencies regression
• #4574; Wrong icons in outline for aspect
• #4768; Many parse error are not reported anymore
• #5000; popup error from the editor when editing those files
• #5047; Import of the same class from different location error is sometime too strict
• #5152; The merger seem to drop the body of my operation

V1.0.0 (29/01/2008)

New features

• Removal of the "kermeta::reflexion" package. This greatly simplifies the reflexivity without loss thanks to the use of aspect on Kermeta framework itself. If some of your code were using it, you simply have to replace all "kermeta::reflexion" by ""kermeta::language::structure".
• Added dedicated keyword "aspect" in order to replace the old @aspect "true" syntax. The old syntax is still supported for backward compatibility.
• Deployment of the first version of a UML MDK for basic support of UML and its profiles. (contributions are welcome)

Bug fixed

• Fixed various bugs in the outline and in the reactivity of the textual editor.

V0.99.0 (21/12/2007)

New features

• Support of OCL syntax (via a transformation to KMT).
• Refactoring of Kermeta Metamodel in order to have a better support of aspects.
• #957; support of platform:// url in the require statement
• #1578; add a open with kermeta graphical editor directly on km files
• #3342; Km2Ecore roundtrip: support of Ecore generics
• #3674; Choice of handling primitive types in Kermeta->Ecore wizard
• #3872; (Kmt/Km)2Ecore action dedicated to metamodel structural part
• #3682; require statement completion
• #4051; Avaibility of EMF Registering/Unregistering actions
• #4063; a copy nsuri from the "EMF registered view"

Bug fixed

• #114; Problem with the definition of a dynamic expression (formal parameters)
• #138; problem with properties that are sets
• #154; the metaclass of the type "kermeta::language::structure::Class"?
• #199; Loading of Ecore Model Failed if the metamodel contains EChar attributes
• #324; Generating Kermeta Source from 2 Ecore Models
• #609; Strange behavior of the type checker for the type of an if condition
• #1124; Possible failure in the inheritance tree. Invoking incorrect operation
• #1161; Declaring bags using the 'bag' keyword and the 'Bag' generic class doesn't work the same way
• #1510; Kmt2Ecore pb when applied to a MM with nested packages
• #1831; Write-only properties don't work
• #1842; the "bag" declaration doesn't work as other collections
• #1865; ecore2km parsing generic type
• #2098; require path problems
• #2182; Null pointer exception when compiling an assignment to a wrong property.
• #2249; Errors are not correcltly reported when a class is re-opened (@aspect "true")
• #3447; OwnedParameters implemented as a set instead of oset
• #3514; aspect weaving does not consider differences in methods signature
• #3638; classes with aspect "true" do not appear in the outline
• #3811; Typechecker problems with aspects
• #4033; Register package fails if the input ecore has no nsURI
• #4097; KET feature dependencies
• #4099; No clear error message when loading two "identical" files
• #4483; unable to override twice toString

V0.5.2 (19/10/2007)

V0.5.1 (20/09/2007)

V0.5.0 (13/07/2007)

New features

Bug fixed

V0.4.2 (11/07/2007)

New features

Bug fixed

• #1021; Enumerations are not handled correctly on load/save EMF models
• #2044; opposite property updating fails
• #3106; loading models from dependent resources should create several resources in kermeta
• #3359; automatic add of the current java project in the run configuration classpath
• #3438; Problems when obtaining enumeration elements from a set
• #3444; In recent releases, the constraint checking is not done in the user interface
• #3519; it should be impossible to add 2 resources with the same uri in a repository
• #3526; Type information isn't correctly saved in .km file
• plus several corections and improvements in the reference manual

V0.4.1 (04/05/2007)

New features

• Metamodel weaving : thanks to the special annotation @aspect it is now possible to separate concerns in several files. It allows to add feature to an existing class. For example you can directly require the original ecore and use aspects to add the behavior or constraints to it. If your behavior needs some additional feature in your class, no problem, add it in the aspect. (#120; Kermeta PackageMerge)
• #277; An OCL like syntax for casting. You can now use something like : myObj.asType(String)
• #971;Getting (numerical) value from a string
• #1493;Need for new operations on Kermeta collections.A number of new operations are now available: Collection.count(); OrderedCollection.indexOf(); Set.intersection(Collection) : Set; Set.union(Set) : Set; Set.unionWithBag(Bag) : Set; Set.minus(Set) : Set; Bag.union(Collection) : Bag; Bag.intersection(Bag) : Bag; Bag.intersection(Set) : Set
• #1933;add new folder button in kermeta perspective
• #1981;when kpm is running it should display it progress in eclipse progress bar
• #2009;Error message should be displayed when kermeta can not launch a file
• #2146;Helpers for reading and writing text files

Bug fixed

• The graphical editor has evolved a little. To improve the abilities of the Kermeta graphical editor, we have modified the presentation parameter of the EMFSemanticModelBridge in *.kmdi file: fr.irisa.triskell.kermeta.graphicaleditor to fr.irisa.triskell.kermeta.graphicaleditor.cd Also, for upgrading your *.kmdi file to the new version: v0.4.0 to v0.4.1, you must edit your old file and replace all the fields: <semanticModel xsi:type="di:EMFSemanticModelBridge" presentation="fr.irisa.triskell.kermeta.graphicaleditor"> by <semanticModel xsi:type="di:EMFSemanticModelBridge" presentation="fr.irisa.triskell.kermeta.graphicaleditor.cd">
• #110; method isInstance on Type not implemented
• #501; kmt2ecore doesn't save attribute generic type and function type into the ecore annotations
• #1127; Reflection does not work for derived properties
• #1586; Type inference failure on type of 'self'
• #1614; parser pb with post and annotations
• #1811; Java error with inherited collections
• #1815; Pb with function variable: no access to Object interface
• #1818; Comparison of objects hashcode in hashtables
• #1893; moving an element from a resource to another doesn't work
• #1910; can not load and save an simple ecore model
• #1932; generic parameters are not displayed correctly in the graphical editor
• #1945; Ecore2Km: pb with string constants
• #2008; Kermeta Samples do not run due to bad launch configurations
• #2112; Reals are impossible to use
• #2114; Error when comparing a collection to void
• #2154; cyclic inheritance
• #2183; internal error if the runconfiguration doesn't provide the expected parameters
• #2198; Infinite loop when saving a model whose MM is available only as generated java
• #2256; Saving a model into a different resource fails
• #2280; Incorrect return value for IF statements

V0.4.0 (28/01/2007)

New features

• Kermeta project nature is now useful: It supports a workbench rule engine for running automated task. So, whenever a file change it can activate some rules. Typically, it will be used to produce a km or an ecore corresponding to a kmt file. The rules can be customized through the kpm model (Kermeta Project Manager) You can even provide your own rules using Eclipse extension points. (In future release you'll be able to run kermeta transformations)
• #1411; add a test that check that java5 is used
• #1291;Improvement of syntax of pre/post conditions

Bug fixed

• Textual syntax for pre and post has been enhanced. The previous version wasn't user friendly. If you want more details about the pre/post new syntax please look this page : http://www.kermeta.org/download/migration_changes/syntax_v032_v040. In order to migrate your files that use the old syntax, we provide a migration tool. (You need to use it only if you have pre and post condition in your kmt files)
• #1746; Texteditor bad Performances when text size increasing. The Text editor is now much more reactive, even on large projects.
• #699; syntaxic colorization problem with special characters in String chains
• #846; bug in method kermeta::language::structure::Class.equals()
• #1085; Kermeta "new file" tabs should be tabs, not spaces !!
• #1165; Kermeta textual editor has problems with comments
• #1213; Managing model dependencies when saving a km files
• #1265; Run a km file
• #1319; kmt 2 km incorrect transformation
• #1463; Error in the method: EMFRepository.load . It sets all EClassinstanceClassName := ""
• #1575; Documentation : Incorrect diagrams in part 3.1.2.2
• #1589; Pb with Resource "contents" and "allContents" properties
• #1675; Pb when using alias types for initializing newly allocated Class elements
• #1678; A Class created at runtime (c := Class.new) is not created correctly
• #1809; Graphical Editor : Restore connection failed with the KermetaStdLib
• #1846; KM2Ecore regression
• #1896; Kmt2Ecore: problem with nested packages
• #1906; Km2Ecore: elts typed by a TypeVariable have no type in Ecore files

V0.3.2 (03/11/2006)

New features

• #1520; Split km model with "Control" shortcut

Bug fixed

• #314; It should not be possible to assign properties with multiplicity > 1
• #1114; Linked comments need quotations
• #1345; Definition of .equals for collection classes
• #1457; Equals and == behavior
• #1536; adding already contained objects to a collection of attribute is impossible and much more
• #1549; Empty iterator body gives bad error message in type checker
• #1550; Cloning collections
• #1561; Refreshment problem in the Km model editor

V0.3.1 (04/10/2006)

New features

• Graphical editor available again (and improved)
• #96; Ability to stop the execution of a kermeta program
• #982; "implies", "xor" and "nand" operators on boolean
• #1264; "Run As" action behaviour
• #1330; A class that contains abstract operations should be semantically abstract, csqtly not instantiable

Bug fixed

• #108; Type checker craches with twice the same primitive type as param of an operation
• #306; Creating a new run configuration does not react when user tries to load a kmt file that has errors
• #601; A few multiplicities in Kermeta metamodel are semantically unconsistant
• #831; the completion proposes the Classes but not the Packages
• #877; kmt2ecore : used of tilda(~) in kermeta files is exactly copied as same in ecore files
• #891; invariant declaration : self overlap in a lambda expression bugs
• #962; Non implemented abstract operation fails without information (only "the node to visit is null")
• #1041; Type Checker does not detect call of [unimplemented] abstract operations
• #1060; Deleting inheritance doesn't affect child Classes
• #1063; initial upper and lower cardinality is set to [0..0]. Expecting [0..1], more consistent
• #1067; Deleting an inheritance edge
• #1115; Annotations are lost when transforming: kermeta to and from ecore
• #1116; Big big big blocks made by the kermeta prettyprinter
• #1126; Invariants are not kept when going from kmt2ecore
• #1154; Control-D key-shortcut gives null pointer error
• #1160; When you click on an invariant in the outline view the editor doesn't go to that invariant
• #1166; Kmt2Km: pb when overloading operations defined in class 'Object'
• #1182; Bug in Ecore2KMT transformation
• #1258; Invariants annotations are lost when moving from KMT to KM
• #1287; Operation pre and post conditions are lost during the Kmt2Ecore2Kmt
• #1293; saving a model in several resources doesn't work correctly if there are Xreferences
• #1297; wrong require statement produces understandable error
• #1302; bug in conversion KMT2Ecore
• #1308; Properties annotations are lost when moving from Ecore to KM

V0.3.0 (19/08/2006)

New features

• This version works with Eclipse 3.2 and EMF 2.2.0, doesn't work correctly anymore with previous versions of EMF

Bug fixed

• #302; More static constraints: redefinition
• #317; {using} before {require} is not detected and execution crashes with no error messages
• #349; detection of wrong require statement
• #351; String pointed as reference : obscure error message
• #353; No exceptions on EMFResource.createresource with non-existing ecore
• #586; package path non complete in generated ecore file
• #617; some tests in the interpreter test suite cannot be run in the same time
• #931; The saving of a executable model in KM form fails on Operation classes
• #951; behaviour of redefinition of "native" operations (example: toString)
• #1017; KUnit fails to intercept some exceptions
• #1069; ecore2kmt quickfixe doesn't succeed to find a problem in case of multiple inheritance

V0.2.2 (22/06/2006)

New features

• #146; Contract support in Kermeta Jean-Marie and Cyril have developped the first version of contracts for Kermeta. It currently uses only Kermeta surface syntax. It fully supports pre/post when calling operations, and provides checkInvariant methods on Object. However, the metamodel is ready to support OCL syntax in the future. The control on pre/post verification is very basic (on/off) and may be improved later
• #520; Multiple Consoles for different Kermeta App Instances

Bug fixed

• #222; console frozen after "generate ecore". Now there is one console per running program.
• #245; aliases not correctly exported to ecore
• #486; pb with kdoc annotations in generated ecore file
• #313; kmt2ecore produces non-conform ecore files
• #619; ecore2kmt doesn't take into account the isAbstract annotation on operations
• #775; ecore2kmt and kmt2ecore: problems with redefined operations
• #808; the "contains" method doesn't work on Class.superType collection
• #843; Bug when loading a model that is an instance of the Ecore.ecore model
• #924; kmt2ecore: problem with inheritance
• #952; The editor tells me about a "INTERNAL ERROR : null" on the first line without any syntax mistake

V0.2.1 (19/04/2006)

Bug fixed

• #192; unable to use the ecore2kmt transformation on ecore.ecore
• #391; load time of the kmt files into the editor (+ duplicate bug #702)
• #620; in ecore2kmt when an operation is redefined, it uses the wrong keyword
• #632; Interpreter can not load models whose generated metamodel contains a "deep" hierachy of package
• #664; ecore2kmt : inherited operations are generated as 'operation' and should be 'method'
• #669; unable to drag'n drop element in subpackages from outline to a diagram
• #670; In diagrams, operation are misplaced in class container
• #672; properties are centered whereas the operations are aligned to the left
• #685; Same property or operation can be displayed several times in the same diagram
• #695; Ecore2Kermeta crashes when there are super operations.
• #718; default name of properties in the editor should use the type name

V0.2.0 (07/04/2006)

New features

• #147; Dedicated Graphical editor for Kermeta This is the first version of a graphical editor for Kermeta (generated with TopcaseD) feel free to report any missing feature and bugs ...
• #255; Metamodel of kermeta km file is not the same as internal kermeta view We have done a big refactoring to the internal EMF structure so it will store kermeta models (ie. *.km files) with exactly the same representation as the one viewed from the reflexivity within Kermeta. Please note that older km file are no longer compatible, you have to regenerate them

Bug fixed

• #328; Round trip kmt2ecore2kmt fails if there are parameters in the operations
• #419; problem with the instances when loading an ecore model
• #454; nsURI/nsPrefix problems when generating ecore from kermeta
• #476; loaded ecore models and instances are uncomplete
• #484; kmt2ecore: pb when a reference, attribute or operation type is not in the generated ecore file
• #485; kmt2ecore should generate only the elements of the current kmt file
• #489; No Ns-Uri for subpackages in generated ecore files
• #495; ecore properties are not implemented in ecore.kmt
• #500; ecore2kmt doesn't use the generic type annotations to generate the kermeta code
• #532; Spelling errors in the kermeta metamodel
• #539; Bug when raising an object that is not an exception
• #562; require "bla.ecore" containing properties using keywords adds incorrect ~ on the property name.
• #577; problems when trying to generate ecore file

Improvements

• Some improvements in the TouchNavigator (graphical improvement and no more hang up on start of the view)

V0.1.1 (30/01/2006)

New features

• #119; Ecore PackageMerge. Simply select 2 or more ecore files and merge them...
• Alpha version of the Class TouchNavigator view. This view will help you to understand your kermeta models in an uncommon way. It dynamically displays a kind of class diagram centered on your selection. Click on an element to expand this node. Let your mouse over a node and it will display the documentation of this class. Feel free to suggest new improvements...

Bug fixed

• #248; kmt2ecore then EMF Java Code Generation produces buggy sources
• #274; Attribute of user-defined type with no opposite generates invalid EMF
• #276; code completion for types causes some nullpointer exception
• #278; Missing methods in class Hastable, added keys() and values() operations.
• #282; Operation Object::isVoid not implemented
• #423; problem when saving a model
• #425; No user java classpath in the Kermeta Run Configuration
• #433; wrong interaction between the run... dialog box and the @mainClass in the kmt file

Improvements

• Update of the user interface documentation.

V0.1.0 (20/12/2005)

New features

• Kermeta has now a debugger ! It has the usual features of debuggers : breakpoints, step in, step over, resume, stop, etc

Bug fixed

• #226; export to ecore fails if no kermeta editor was opened in a session
• #244; kermeta2ecore doesn't affect a default value for NS_URI. The generated default uri use a relative path.
• Some correction on exception handling

Improvements

• Some improvements in the content of the hovertext in the text editor
• Update of the interpreter javadoc in the eclipse help.

V0.0.18 (02/12/2005)

Improvements

• #275; default implementation of the operation body should raise an exception if used
• Added some checks of static contraints on kermeta programs (see #298; Static constraints on Kermeta programs)

Bug fixed

• #102; Run as Kermeta App does not work if no configuration has been created before
• #149; Warning in imported files a treated as errors
• #211; Load model error reporting is poor
• #279; Escape character \ not handeled corectly in strings
• #281; Bug in method String::substring
• #283; warning in imported unit messages are placed on top of the file instead of in front of the correct require statement
• #284; no way to pass command line arguments from the run configuration
• #308; Problem with containment when saving a model

V0.0.17 (09/11/2005)

Improvements

• #239; Request for "forAll" and "Exists" operations
• Some updates in the documentation

Bug fixed

• #149; Warning in imported files a treated as errors
• #227; not able to load a km file as a model. (and also problem loading ecore file as models)
• #228; km files contains tags corresponding to the framework
• #273; Backslashed bakcslash inside double-quoted string
• #164; location of the error if the error is discovered at run time (Partial fix, it correctly displays the error if it comes from a kmt file but not from a km file)

Other

• Kermeta Eclipse update site has changed: http://www.kermeta.org/update
• various models are now deployed within the Kermeta plugin (kermeta.ecore, kermeta_java.ecore, ecore.ecore, ecore.kmt)

V0.0.16 (12/09/2005)

Improvements

• Better interpreter performances. (Increased by 20)
• New tutorial about load and save EMF model with Kermeta

Bug fixed

• some minor bug fixes

V0.0.15 (30/08/2005)

Improvements

• better exception handling

Bug fixed

• #143;bug in model loading
• #98;Kermeta documentation unavailable under Eclipse
• #122uncompatibility with eclipse 3.1

V0.0.14 (22/08/2005)

New features

• save of EMF model instances from kermeta to xmi files and load EMF xmi->Kermeta.
• support of the traceability model for transformations kmt2ecore, kmt2km, km2ecore and ecore2kmt(partial)
• ecore2kermeta transformation improved for ecore models that contain operation bodies stored as annotations

Improvements

Bug fixed

• #125; in the wizards, if the default file name already exist there no error message
• #85;out of Memory when interpreting
• #109;derived property not implemented
• #100;problems with file creation tools under Eclipse

V0.0.13 (22/07/2005)

New features

• load of model instances stored in xmi into kermeta.
• kermeta2ecore transformation (kermeta bodies are stored in annotations)
• km2kermeta, km2ecore transformations

Improvements

• ecore2kermeta uses a wizard to allow control on some simple quick fixes done during the transformation.
• better error reporting on all xxx2yyy transformations.

Bug fixed

• #92; Kermeta files always created in the root directory of the project
• #95; some images don't appear in the generated documentation (wmf images in metamodel doc)
• #100; the button "Create new K. File" does not do anything
• #103; the selection is not taken into account when creating a new kermeta file with the wizard
• #105; compile 2 XMI fails
• #117; method Hashatable.get in the framework

V0.0.12 (13/07/2005)

• Many bug fixes, (including an annoying OutOfMemory error).
• Improvement of the launch menu. (faster and more reliable).
• Implementation a clone method.
• Development  CVS moved to gforge.inria.fr

V0.0.7 (03/06/2005)

Improvements

• Bug fix in the transfo ecore 2 kermeta
• Bug fix in the interpretation of lambda expressions

GUI improvements

• Memory leak fixed in the plugin
• ID of the text editor fixed

Known limitations (not implemented and/or not tested)

• derived properties not implemented
• Annotations processing needs to be fixed
• The use of non unique properties has a random behavior
• Error reporting when an exception is raised should be improved (acsessing the stack trace in kermeta should be possible)

Known bugs

• Run does not work correctly under windows
• a ; after require kermeta invalidate the remaining of the kmt file
• product types cannot reference twice the same type
• The interpreter uses too much memory.

V0.0.6 (01/06/2005)

GUI improvements 

• Kermeta perspective
• Kermeta project / file
• Kermeta run compatible with "eclipse run policy" improvements
• Transformation ECore 2 Kermeta available
• Added support for exception handeling
• Support for containement and opposite properties fixed
• Added support for dynamic casts
• Reflection on generic types fully implemented

V0.0.5 (20/05/2005)

Improvements

• Added suport for Enumerations
• Bug fix in the framework and interpreter

V0.0.4 (17/05/2005)

features (not fully tested)

• Texteditor
• Outline
• Run from the resou
• Help

known limitations (not implemented and/or not tested)

• exceptions can be thrown but not caught
• Enumeration cannot be used
• Casts are not checked
• handling of opposite property does not work properly
• handling of objects contained does not work properly
• Reflection on generic types is not fully implemented
• framework is not complete and not fully tested known bugs
• a ; after require kermeta invalidate the remaining of the kmt file
• product types cannot reference twice the same type