Closed izsob closed 12 years ago
Lovely!
Anatomy: unless we initialize the IQRuntime first as a workaround (such as by the logger invocation), calling generated code will
IncQueryMatcher
in particular), whichIncQueryMatcher
, and thus Is this an Eclipse 4 "feature"? If yes, then E4 is really weirdly broken.
How do we fix this? Isolate the matcher registry and associated services to a separate bundle?
I think this is a severe issue which needs to be fixed before any public "release".
@bergmanngabor , could you implement a lazy loading scheme as discussed with @ujhelyiz on skype?
@izsob can you please try again whether the issue can be reproduced with the newest version?
The issue can be reproduced with version 0.6.0.201208091120.
Did you use the update site version? That has finished only at 13:45...
@izsob please try again with the most current build.
I use the CI update site, and now I could update to another version: 0.6.0.201208091147 Now I can not reproduce the issue.
Then let's assume it was fixed.
Please run whathever tests we have manually before release.
I have run the school and ecorequery tests. The original tests using the generic API were extended with alternative versions using the generated matcher factories (although none of the pattern-specific generated methods are tested yet).
although none of the pattern-specific generated methods are tested yet
We use pattern-specific generated methods and they run.
EMF-IncQuery throws ClassCircularityError when the first line is commented:
Workaround: uncomment the getDefaultLogger() call.
Stack trace: