moosetechnology / famejava

Fame is a concise meta-meta-model, and this project holds its Java implementation. This is a fork of the original implementation by Adrian Kuhn and Toon Verwaest.

Fame-Java

Fame is a concise meta-meta-model. This is a fork of the original Fame meta-meta-model implementation by Adrian Kuhn and Toon Verwaest.

This is an implementation of Fame in Java that supports traits concept used in the last Famix

User

To generate the java classes of a Moose meta-model:

1. generate (in Pharo) a .mse file describing the meta-model. command: 'some-file-name.mse' asFileReference writeStreamDo: [:stream | MooseModel metamodel exportOn: stream]
2. add the .mse file under the "resources" folder.
3. under "src/metamodel.codegen" create a new "target" following the template of other Codegen class.
4. execute the "target" to generate the code under the folder gen.

License: GNU LESSER GENERAL PUBLIC LICENSE

famejava's Issues

JSON ouput: " in strings should be escaped

otherwise we get lines as "signature":"print("Printer " + name() + " prints "+ thePacket.contents(),false)" which produce error

export of metamodel to Java

When exporting metamodel to Java, the inheritance between traits is not exported:

Trait << #FamixTType
	traits: {FamixTNamedEntity + FamixTReferenceable + FamixTSourceEntity + TEntityMetaLevelDependency};

gives:

public interface TType  {

whereas it should be:

public interface TType  extends  TNamedEntity, TReferenceable, TSourceEntity, TEntityMetaLevelDependency {

Handle submetamodels with inheritance

if we have 2 meta-models mm1 and mm2, mm1 is sub-meta-model of mm2 (ie. mm2 uses entities of mm1).

there is an mm1Entity and an mm2Entity and they don't inherit one from the other

If both generators are based on FamixBasicInfrastructureGenerator, then there are also two SourcedEntity, NamedEntity, Comment, ...

when we translate that to Java, we have "incompatible types", eg two NamedEntity.java that are equals but in separate packages and incompatible ...

Default value for Properties

We need to add the support of default value for properties.
It implies modifying the Fame Meta-model, the .mse importer, and the code generator.

This feature exists in Fame Pharo

Importer does not understand the property `users` on FM3Trait

When exporting the Java metamodel with:

'famixJava.mse' asFileReference writeStreamDo: [:stream | FamixJavaModel metamodel exportOn: stream]

We have the property users under trait elements.
The importer does not understand that property and raises an error.