Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

language runtime not detected and generate MT fail for an ecore named "testMM_Foo.ecore" #95

Open
dvojtise opened this issue Oct 23, 2017 · 2 comments
Labels

Comments

@dvojtise
Copy link
Contributor

dvojtise commented Oct 23, 2017

it seems that Melange has issue for some ecore when they used some names such as "testMM_Foo.ecore".

for such ecore, the warning about "Cannot find EMF runtime for ..." is never fixed even if the corresponding project has been correctly generated. In addition, the code for the model type (*MT.java") is not generated

The crash does NOT produce any trace in any of the log or consoles 😢

procedure : (I used GEMOC studio 2.3.0 and 3.0.0)

  • New ecore Modeling project, use a name with uppercase and underscore such as "testMM_Foo" (I still don't know if this is the underscore or the uppercase that make this issue
  • add a few classes (2 is enough), then generate model code
  • create a melange project and language that refer it. For convenience, simply use Gemoc "new GEMOC sequential project" and one of its templates
  • on the .melange file, generate all (the runtime project it there but the warning on the language is still here) the src-gen folder will NOT have any *MT.java file. you can try to launch the different action separately but with no help.

(project for verification)
MelangeIssue_testMM_Foo.zip

@dvojtise dvojtise added the bug label Oct 23, 2017
@dvojtise
Copy link
Contributor Author

2 test later : apparently this is the use of camel case in the ecore/epackage/project that doesn't work
a project named testMmFoo fails but testmm_foo works.

@fcoulon fcoulon reopened this Oct 23, 2017
@fcoulon
Copy link
Contributor

fcoulon commented Oct 23, 2017

Can you confirm the fix?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants