|
Re: Xtext & Build Loops [message #1850846 is a reply to message #1850837] |
Fri, 18 March 2022 12:16   |
Eclipse User |
|
|
|
Hi
Great news. This is very encouraging.
My attempts to investigate in the past were hampered by no obviously good .options setting to enable the recursions to be logged. No advice was forthcoming.
Is there now a .options that can be set to log each build activation?
It is unlikely that the Xtext builder is the only builder with sub-optimal strategy. A .options that enables other builders to be diagnosed would be good.
Regards
Ed Willink
|
|
|
|
Re: Xtext & Build Loops [message #1850855 is a reply to message #1850848] |
Fri, 18 March 2022 16:08   |
Eclipse User |
|
|
|
Hi
Thanks not aware of the Xtext Console.
It certainly gives me a key to some total time burners such as:
[Worker-41: Build Project] indexing platform:/resource/org.eclipse.uml2.uml/model/UML30.ecore
Why is a *.ecore in a project without an Xtext nature indexed?
Why after cleaning org.eclipse.ocl.examples.build is org.eclipse.uml2.uml re-indexed? Ok it's transitively referenced but it's not dirty and not clean all.
Regards
Ed Willink
|
|
|
Re: Xtext & Build Loops [message #1850858 is a reply to message #1850855] |
Fri, 18 March 2022 16:38   |
Eclipse User |
|
|
|
i believe the ecore thing was discussed in a bugzilla i cannot find between sebastian and you before.
and no we did not change any logic in xtext. we just call tell the platform to rebuild the current project
and not all projects as we did before.
what does the log tell when you see the indexing message.
which project is it building?
[Updated on: Fri, 18 March 2022 17:00] by Moderator Report message to a moderator
|
|
|
|
Re: Xtext & Build Loops [message #1850885 is a reply to message #1850861] |
Mon, 21 March 2022 08:38   |
Eclipse User |
|
|
|
Hi
Still using 2022-03, I now have the Xtext Build Console active and can see that most of the time, everything is reasonable, a build is requested and nothing needs doing.
But sometimes there is action and I can now go back and investigate after the event, but ...
It would be really helpful if as well as the Built elapsed time at the end there was a Building absolute start time at the front, and possibly a diagnosis of the build trigger (at least full/incremental and maybe the dirty files list).
(The triggers could help identify why a real build seems to have a no-action build just before and just after.)
Regards
Ed Willink
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03373 seconds