A. Are you saying that JetBrains has no interest in fixing the Eclipse plug-in?
The development of the Eclipse Plug-in slowed down, because the main developer was given another task. But JetBrains said that the development should go on.
B. The programming staff I work with uses Eclipse for a variety of workflows, in several programming languages. For a variety of reasons, we have no interest in changing to IntelliJ. If we have to stay with Java to stay with Eclipse, we will.
That is understandable. Personally I prefer IntelliJ, but I know enough developers that are happy with Eclipse. I don’t think that it was JetBrains driving motivation to “lure” programmers into their camp. However, they don’t say “no” to a new customer who was attracted by Kotlin. The main problem is that the Eclipse community didn’t pick up the initial work from JetBrains. In the long-term Kotlin for Eclipse has to be community driven.