pyecore / pyecoregen

99%

master: 100%

LAST BUILD ON BRANCH 0.1.0

branch: 0.1.0

CHANGE BRANCH

x

Reset

• 0.1.0
• 0.0.1
• 0.0.2
• 0.1.1
• 0.2.0
• 0.3.0
• 0.4.0
• 0.4.1
• 0.4.2
• 0.4.3
• 0.5.0
• 0.5.1
• feature/default_values
• feature/derived_changeable_attribute
• feature/derived_collections
• feature/generics
• feature/global-context
• feature/http_uri
• feature/kind_type
• feature/metamodel-dependencies
• feature/name-adaptation
• feature/package_autoregistration
• feature/remove-python3.3
• feature/upgrade-pythonversion
• feature/userclass
• fix/eattribute_unique
• fix/eoperation_documentation
• fix/missing-edatatype
• hotfix/failing-tests
• hotfix/missing-templates
• master

Build # 13

Build Type

push

travis-ci

Committed by aranega

Commit Message

Remove loaded metamodel registering in the ResourceSet

If a metamodel is loaded, its registration in the global_registry or
the ResourceSet metamodel_registry is only required if an instance of
this metamodel is going to be loaded. In the case of the Ecore2Python
generation, the instance model is an Ecore instance metamodel. Thus,
the loaded metamodel is seen as an Ecore instance and it is not
required to register it in a metamodel_registry.

Run Details

137 of 139 relevant lines covered (98.56%)

3.94 hits per line