[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [incquery-dev] misc notes on the xcore issue
|
Hi,
luckily the PDE issue got fixed quickly.
On the other hand, I have found a really nice (not) name clash in the generated code of the library example:
* The library.xcoreeiq file defines a class named Library, from which an interface library.Library should be generated
* The library.eiq file is used to generate a pattern group with the fqn name of library.Library
This does not seem healthy to me, and might cause some tricky issues. For now, in my workspace I have renamed library.eiq to libraryQueries.eiq just to be on the safe side...
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 2013.10.15., at 11:50, Tamas Szabo <tamas.szabo@xxxxxxxxx> wrote:
> Hi
>
> I have created a pde.core bugzilla issue in the context of our issue (https://bugs.eclipse.org/bugs/show_bug.cgi?id=419128).
> I have patched myself the pde.core plugin and with that version (on my machine) all of the xtext 2.5 related Exceptions are gone.
> I cleaned the library project many times, built it many times, etc...
>
> Regarding the @Ecore annotation (in xcoreiq) and its effect for rewriting the plugin.xml with the new nsUri;
> - for the first time a <!-- @generated library --> comment is placed into the plugin.xml for the generated package entry.
> - this will be removed during the IncQuery generator phase
> - from this point the xcore generator is unable to update the entry with the new nsUri because it is looking for this comment.
>
> Regards,
> Tamas
> _______________________________________________
> incquery-dev mailing list
> incquery-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/incquery-dev
