Hi,
I do know that nothing has changed. And no, it does not help with a new workspace.
That is the reason why I am so puzzled that *exactly* the same issue that happened yesterday for the Oxygen nightly build (which was fixed with today's build), now happens for the Neon daily build. Especially since nothing as you say actually have changed.
I am using an Oomph setup file together with the Eclipse Installer to perform my installations of Papyrus. I can say also that the same issue pops up in the context of Papyrus-RT, so I actually have exactly the same issue for my Papyus-RT testing (which is based on the latest nightly build of Papyrus Neon). The Oomph setup file used for Papyrus-RT can be found here
https://www.eclipse.org/papyrus-rt/content/setup/papyrus-rt-tester.setup
Sure, it could be an issue with my p2 bundle pool for the Eclipse Installer that has gone "bananas" (since I am using a shared bundle pool for all my different Papyrus and Papyrus-RT installations).
If you say that it works for you, then I guess I need to do some more testing on my side.
/Peter Cigéhn