| How to exclude resources from build [message #1766777] |
Tue, 27 June 2017 04:42  |
Eclipse User |
|
|
|
Hello,
I am trying to speed up my xbase language, and I have learned a lot of Scoping, Containers, Linking, ..., but I was not successful to speed up my language in a way my colleagues would like to work with it. The performance slows down when language files are increasing, so a full build takes 15 sec if only one project is open (normally we have 6-7 projects open -> this is more than a minute).
Now I dug a bit and found that files in jars are parsed, no problem as they might be needed for global linking, but these resources are not only parsed but passed to EcoreUtil2.resolveLazyCrossReferences in Step 6 of ClusteringBuilderState. This causes the resource to be parsed again and the linking takes most of the time. Now the problem is, that 90% of these files are not used for global scoping, only the generated classes are referenced, an they are already included in the jar file.
I have created my own ResourceDescriptionStrategy to make sure that no EObjectDescription is created, but this has no effect.
My guess would be to create my own ClusteringBuilderState, but I doubt that this is the right solution.
So my question is: Is there a better way how to exclude resources, which are not used in global scoping?
Any hint welcome.
I am still using xtext 2.9.2.
Thank you
|
|
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03425 seconds