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

Loading of Ecore models depends on side effects #1

Open
tvdstorm opened this issue Sep 8, 2017 · 1 comment
Open

Loading of Ecore models depends on side effects #1

tvdstorm opened this issue Sep 8, 2017 · 1 comment
Labels

Comments

@tvdstorm
Copy link
Member

tvdstorm commented Sep 8, 2017

To reproduce:

@tvdstorm tvdstorm added the bug label Sep 8, 2017
@tdegueul
Copy link
Collaborator

tdegueul commented Sep 8, 2017

Related to the classpath problems I guess.

Ecore is registered in Eclipse's EPackage.Registry at startup time, but the Rascal console creates another EPackage.Registry in a different classpath, so it does not work the first time.

Loading any model will register Ecore in the registry if it's not there already, so it will work the second time.

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