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

ConfigurationScript metamodel import Error. Couldn't resolve reference to EPackage #17

Open
vnikitch opened this issue Oct 11, 2018 · 0 comments

Comments

@vnikitch
Copy link

JUnit test failed on test project "hu.bme.mit.inf.dslreasoner.application.FAMTest"
https://github.com/viatra/VIATRA-Generator/tree/master/Tests/hu.bme.mit.inf.dslreasoner.application.FAMTest

java.lang.AssertionError: expected:<null> but was:<The Configuration Script contains 2 errors:
Couldn't resolve reference to EPackage 'inputs/FamMetamodel.ecore'.
Couldn't resolve reference to EPackage 'functionalarchitecture'.

at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at hu.bme.mit.inf.dslreasoner.application.FAMTest.StandaloneScriptExecutionTests.runWithPath(StandaloneScriptExecutionTests.java:12)
at hu.bme.mit.inf.dslreasoner.application.FAMTest.StandaloneScriptExecutionTests.runWithPath(StandaloneScriptExecutionTests.java:21)
at hu.bme.mit.inf.dslreasoner.application.FAMTest.StandaloneScriptExecutionTests.generateFAM(StandaloneScriptExecutionTests.java:56)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:541)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:763)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:463)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:209)

The project contains file with name "generation.vsconfig" in a inputs folder. It looks like it was created correctly respecting all constraints. But import section doesn't work for me. I tried to create my own .vsconfig files then invoking StandaloneScriptExecutor.executeScript(path) method gives the same error

One of the possible solution may be to provide built version of VIATRA-generator. (According to wiki Installation Guide the only way to install this plugin is to build from source code). The user's environment may differ from the developer's and this may cause problems

I would like to ask you to provide more details on launching your model generator

@vnikitch vnikitch changed the title ConfigurationScript metamodel import Error ConfigurationScript metamodel import Error. Couldn't resolve reference to EPackage Oct 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant