[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [incquery-dev] IInputKey cannot be resolved
|
Yes, I second Gábor that this seems like an incorrect cache issue: the runtime Eclipse did not detect changes in the source project, and a series of F5/Refresh presses should fix this.
Maybe a Plug-in tools/Update classpath execution on the runtime project might also help; or simply rebuilding the target platform.
Cheers,
Zoli
-- Zoltán Ujhelyi
https://www.inf.mit.bme.hu/en/members/ujhelyiz
Fault Tolerant Systems Research Group
Budapest University of Technology and Economics
On 2015.04.25., at 20:18, Bergmann Gábor wrote:
> Hi,
>
> I use a similar setup (building stuff from source, then running the runtime workspace), and have not encountered any such problems (that’s why I dared push it to master in the first place).
>
> Zoltán has this usual trick to select “Plug-In Dependencies” and hit F5 – that seems to resolve these weird cache symptoms sometimes. Hope that helps. Other than that, I’m just as baffled as you.
>
> Sorry for the inconvenience,
> Gábor
>
>
> From: Harmath Dénes
> Sent: Saturday, April 25, 2015 12:10 PM
> To: Incquery developer discussions
> Subject: [incquery-dev] IInputKey cannot be resolved
>
> Hi everybody,
>
> using latest EMF-IncQuery from source (commit ed8ccaf), after regenerating the code for my patterns (in a runtime Eclipse), the generated QuerySpecification classes have compile errors on the TypeConstraint constructor calls:
>
> - The type org.eclipse.incquery.runtime.matchers.context.IInputKey cannot be resolved. It is indirectly referenced from required .class files
> - The constructor TypeConstraint(PBody, Tuple, IInputKey) refers to the missing type IInputKey
>
> As well as the project containing the pattern code:
>
> The project was not built since its build path is incomplete. Cannot find the class file for org.eclipse.incquery.runtime.matchers.context.IInputKey. Fix the build path then try building this project
>
> What I tried:
>
> • Adding org.eclipse.incquery.runtime.matchers to the build path of this project (org.eclipse.incquery.runtime was already a dependency, it shadowed org.eclipse.incquery.runtime.matchers, so had to be removed and readded afterwards)
>
> • Deleting the src-gen folder, cleaning the project, modifying the EIQ file to have the code regenerated
>
> • Cleaning EMF-IncQuery sources and rerunning the Oomph setup of EMF-IncQuery
>
> Neither of these helped. What could I do?
>
> Thanks in advance!
> Dénes
>
>
> --------------------------------------------------------------------------------
> _______________________________________________
> incquery-dev mailing list
> incquery-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/incquery-dev
> _______________________________________________
> incquery-dev mailing list
> incquery-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/incquery-dev
