Community
Participate
Working Groups
Build Identifier: 20100218-1602 from my forum post... i d/l the latest version of epsilon (0.9.0.201011251259), and while testing it i realized that the "synchronize GMF gen model" option on the .gmfgen model is causing an error when accidentally used more than once. it does not have an effect on the model however (the .gmfgen is not damaged), but nevertheless i thought it might me interesting for you to know. would have filed a bug report, but for some reason i couldn't find the eugenia component in bugzilla... Confused cheers marco ps: ok now that i took a closer look at the error message i know what's causing it. in my FixGMFGen.eol i remove an entry from a toolgroup. GmfGen!ToolGroup.all.selectOne(r|r.title = 'Connections').entries.remove(GmfGen!ToolEntry.all.selectOne (r|r.title = 'RealizedTestPurpose')); so when this is called a second time, the entry is not found anymore -> error. for some reason this error was suppressed (or not arising) in the version i was using before (0.8.0...). dunno if this is a problem or not... Internal error: java.lang.IllegalArgumentException 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.eclipse.epsilon.eol.util.ReflectionUtil.executeMethod[Re flectionUtil.java:183] at org.eclipse.epsilon.eol.util.ReflectionUtil.executeMethod[Re flectionUtil.java:164] at org.eclipse.epsilon.eol.execute.PointExecutor.executeOperati on[PointExecutor.java:161] at org.eclipse.epsilon.eol.execute.PointExecutor.execute[PointE xecutor.java:74] at org.eclipse.epsilon.eol.execute.PointExecutor.execute[PointE xecutor.java:42] at org.eclipse.epsilon.eol.execute.PointExecutor.execute[PointE xecutor.java:130] at org.eclipse.epsilon.eol.execute.ExecutorFactory.executeAST[E xecutorFactory.java:179] at org.eclipse.epsilon.eol.execute.StatementBlockExecutor.execu te[StatementBlockExecutor.java:33] at org.eclipse.epsilon.eol.execute.ExecutorFactory.executeAST[E xecutorFactory.java:179] at org.eclipse.epsilon.eol.EolModule.execute[EolModule.java:57] at org.eclipse.epsilon.eugenia.EugeniaActionDelegate.runImpl[Eu geniaActionDelegate.java:168] at org.eclipse.epsilon.eugenia.EugeniaActionDelegate$1.run[Euge niaActionDelegate.java:81] at org.eclipse.core.internal.jobs.Worker.run[Worker.java:55] (D:\workspaces\workspace\de.fraunhofer.fokus.testing.fokusmb t.diagram.gmf.testpurpose\model\FixGMFGen.eol@86:66) 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.eclipse.epsilon.eol.util.ReflectionUtil.executeMethod(Re flectionUtil.java:183) at org.eclipse.epsilon.eol.util.ReflectionUtil.executeMethod(Re flectionUtil.java:164) at org.eclipse.epsilon.eol.execute.PointExecutor.executeOperati on(PointExecutor.java:161) at org.eclipse.epsilon.eol.execute.PointExecutor.execute(PointE xecutor.java:74) at org.eclipse.epsilon.eol.execute.PointExecutor.execute(PointE xecutor.java:42) at org.eclipse.epsilon.eol.execute.PointExecutor.execute(PointE xecutor.java:130) at org.eclipse.epsilon.eol.execute.ExecutorFactory.executeAST(E xecutorFactory.java:179) at org.eclipse.epsilon.eol.execute.StatementBlockExecutor.execu te(StatementBlockExecutor.java:33) at org.eclipse.epsilon.eol.execute.ExecutorFactory.executeAST(E xecutorFactory.java:179) at org.eclipse.epsilon.eol.EolModule.execute(EolModule.java:57) at org.eclipse.epsilon.eugenia.EugeniaActionDelegate.runImpl(Eu geniaActionDelegate.java:168) at org.eclipse.epsilon.eugenia.EugeniaActionDelegate$1.run(Euge niaActionDelegate.java:81) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Reproducible: Always
We improved error reporting during the 0.9.x branch, so it may have been silently dropped before (but not anymore). Closing as invalid for the time being. If you run into any more trouble, please feel free to reopen the bug :-).