Community
Participate
Working Groups
In some cases the generated code on basis of an active annotations is dependent on the application of another active annotation. However, cycles cannot always be detected correctly (e.g. newly generated classes/interfaces etc). In such cases a multiple-pass approach of processing active annotations would help. In my concrete use case, I even could not find any workaround, i.e. the project cannot be built from scratch in a clean way and after the basic build I have to open each xtend file, add a whitespace (change the file) and save/compile again. So in the end I have two passes and it works then. (cp. https://groups.google.com/forum/#!topic/xtend-lang/t6awI3v3LKA)
Could you provide a concrete example, in which case an extra spin would be necessary?
Created attachment 257940 [details] Active Annotations for Extension Classes
I've added a short example which shows the reported behavior. Let Eclipse build everything from scratch and it will result in two errors ("Component.xtend" and "Extensions.xtend"). Just opening these files, adding a space, or something, and save does the Job. Afterwards, everything works.
