Hi again,
I have now tried the latest patch set 8, and the Mylyn pre-configured queries works. We are getting there... :)
Next step I tried starting a runtime workbench, and started testing a bit. But then I bumped into the same kind of issue I did in my nightly build test installation. And we once again bump into this confusion about "nightly builds". I see that you have chosen the ${base.downloads.url}/papyrus-rt/builds/nightly/ as the repo for downloading "nightly" builds for the codegen/runtime parts, instead of ${base.downloads.url}/papyrus-rt/builds/repo/ (which is the one that I would have picked).
I really think that for consistency the repo-repo shall be used (since the build of that one is triggered directly by a push to master, in the same way as the "nightly" builds for the core/profile/tooling parts in the repo on Hudson).
We really need to settle this about "nightly builds", i.e. whether they should be a time trigger built every 24 hours, or if a "nightly build" is built as soon (within 20 minutes) as new push has been made to the master branch. Personally I really do not see the need for having to wait 24 hours to get a "nighty build", at least not for developers who want to be working on the "bleeding edge".
But maybe I am wrong. But currently we have it very inconsistent where we pick up 20-minute builds for the core/profile/tooling and 24-hour builds for the codegen/runtime parts. I really think that we need to be consistent. And we should at least get one 24-hour build for the codegen/runtime parts to have succeeded so that we can have a consistent neon target definition in the runtime workbench.
/Peter Cigéhn