Eclipse Community Forums: EMF-IncQuery » Error executing EValidator

Home » Archived » EMF-IncQuery » Error executing EValidator

Error executing EValidator [message #1067714]

Wed, 10 July 2013 05:30

Eclipse User

After a workspace build I get "Error executing EValidator" for two of my
query files. What is this supposed to mean?

best regards,
Jan

Re: Error executing EValidator [message #1067715 is a reply to message #1067714]

Wed, 10 July 2013 05:34

Eclipse User

Hi Jan,

this means one of our validators have thrown an unexpected exception. This is more then likely a bug in our validators (it might be some issue with your input too, but our validators should not throw unhandled exceptions). Could you look at the Error log view for an exception trace?

Thanks,
Zoltán

Re: Error executing EValidator [message #1067731 is a reply to message #1067715]

Wed, 10 July 2013 06:28

Eclipse User

Hi Zoltan,
I get the following trace. But I cannot really understand it because my
project is open.

best regards,
Jan

java.lang.IllegalArgumentException: Invalid project org.myproject.test.
Only existing, open plug-in projects are supported by the generator.
at
com.google.common.base.Preconditions.checkArgument(Preconditions.java:88)
at
org.eclipse.incquery.tooling.core.project.ProjectGenerationHelper.checkBundleDependency(ProjectGenerationHelper.java:267)
at
org.eclipse.incquery.patternlanguage.emf.ui.validation.GenmodelBasedEMFPatternLanguageJavaValidator.checkImportDependency(GenmodelBasedEMFPatternLanguageJavaValidator.java:122)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.eclipse.xtext.validation.AbstractDeclarativeValidator$MethodWrapper.invoke(AbstractDeclarativeValidator.java:115)
at
org.eclipse.xtext.validation.AbstractDeclarativeValidator.internalValidate(AbstractDeclarativeValidator.java:292)
at
org.eclipse.xtext.validation.AbstractInjectableValidator.validate(AbstractInjectableValidator.java:66)
at
org.eclipse.xtext.validation.CompositeEValidator.validate(CompositeEValidator.java:127)
at
org.eclipse.emf.ecore.util.Diagnostician.doValidate(Diagnostician.java:171)
at
org.eclipse.emf.ecore.util.Diagnostician.validate(Diagnostician.java:158)
at
org.eclipse.emf.ecore.util.Diagnostician.validate(Diagnostician.java:137)
at
org.eclipse.xtext.validation.CancelableDiagnostician.validate(CancelableDiagnostician.java:36)
at
org.eclipse.emf.ecore.util.Diagnostician.doValidateContents(Diagnostician.java:181)
at
org.eclipse.xtext.validation.CancelableDiagnostician.doValidateContents(CancelableDiagnostician.java:48)
at
org.eclipse.xtext.xbase.validation.XbaseDiagnostician.doValidateContents(XbaseDiagnostician.java:46)
at
org.eclipse.emf.ecore.util.Diagnostician.validate(Diagnostician.java:161)
at
org.eclipse.emf.ecore.util.Diagnostician.validate(Diagnostician.java:137)
at
org.eclipse.xtext.validation.CancelableDiagnostician.validate(CancelableDiagnostician.java:36)
at
org.eclipse.emf.ecore.util.Diagnostician.doValidateContents(Diagnostician.java:185)
at
org.eclipse.xtext.validation.CancelableDiagnostician.doValidateContents(CancelableDiagnostician.java:48)
at
org.eclipse.xtext.xbase.validation.XbaseDiagnostician.doValidateContents(XbaseDiagnostician.java:46)
at
org.eclipse.emf.ecore.util.Diagnostician.validate(Diagnostician.java:161)
at
org.eclipse.emf.ecore.util.Diagnostician.validate(Diagnostician.java:137)
at
org.eclipse.xtext.validation.CancelableDiagnostician.validate(CancelableDiagnostician.java:36)
at
org.eclipse.emf.ecore.util.Diagnostician.validate(Diagnostician.java:120)
at
org.eclipse.xtext.validation.ResourceValidatorImpl.validate(ResourceValidatorImpl.java:141)
at
org.eclipse.xtext.xbase.annotations.validation.DerivedStateAwareResourceValidator.validate(DerivedStateAwareResourceValidator.java:33)
at
org.eclipse.xtext.validation.ResourceValidatorImpl.validate(ResourceValidatorImpl.java:99)
at
org.eclipse.xtext.ui.validation.DefaultResourceUIValidatorExtension.addMarkers(DefaultResourceUIValidatorExtension.java:60)
at
org.eclipse.xtext.ui.validation.DefaultResourceUIValidatorExtension.updateValidationMarkers(DefaultResourceUIValidatorExtension.java:45)
at
org.eclipse.xtext.builder.builderState.MarkerUpdaterImpl.processDelta(MarkerUpdaterImpl.java:72)
at
org.eclipse.xtext.builder.builderState.MarkerUpdaterImpl.updateMarkers(MarkerUpdaterImpl.java:57)
at
org.eclipse.xtext.builder.builderState.AbstractBuilderState.updateMarkers(AbstractBuilderState.java:80)
at
org.eclipse.xtext.builder.clustering.ClusteringBuilderState.doUpdate(ClusteringBuilderState.java:262)
at
org.eclipse.xtext.builder.builderState.AbstractBuilderState.update(AbstractBuilderState.java:111)
at
org.eclipse.xtext.builder.impl.XtextBuilder.doBuild(XtextBuilder.java:184)
at
org.eclipse.xtext.builder.impl.XtextBuilder.fullBuild(XtextBuilder.java:210)
at org.eclipse.xtext.builder.impl.XtextBuilder.build(XtextBuilder.java:89)
at
org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:726)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
at
org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
at
org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351)
at
org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374)
at
org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)

Zoltan Ujhelyi wrote:
> Hi Jan,
>
> this means one of our validators have thrown an unexpected exception.
> This is more then likely a bug in our validators (it might be some issue
> with your input too, but our validators should not throw unhandled
> exceptions). Could you look at the Error log view for an exception trace?
>
> Thanks,
> Zoltán

Re: Error executing EValidator [message #1067737 is a reply to message #1067731]

Wed, 10 July 2013 07:33

Eclipse User

Hi,

I would like to ask whether your project is an eclipse plug-in project? If you have created it using the EMF-IncQuery project wizard, then it should be (the wizard creates an IncQuery project that is both a Java project and an Eclipse plug-in project).

However, the message and the trace does not make sense otherwise (the editor must be open from a project that is not closed).

Cheers,
Zoltán

Re: Error executing EValidator [message #1067756 is a reply to message #1067737]

Wed, 10 July 2013 09:05

Eclipse User

Thx Zoltán,
my project was no plugin project since it's only for some testing. I
converted it and now the error isn't thrown anymore.

best regards,
Jan

Zoltan Ujhelyi wrote:
> Hi,
>
> I would like to ask whether your project is an eclipse plug-in project?
> If you have created it using the EMF-IncQuery project wizard, then it
> should be (the wizard creates an IncQuery project that is both a Java
> project and an Eclipse plug-in project).
>
> However, the message and the trace does not make sense otherwise (the
> editor must be open from a project that is not closed).
>
> Cheers,
> Zoltán

Previous Topic:	After each workspace build every pattern has the same error
Next Topic:	Different Results when usin API in runtime Eclipse and in JUnit Plugin Test

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Jul 24 17:51:05 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter