Practical and Theoretical Limitations Imposed by Buildship and the Eclipse Project Model

Posting here since I received no response on the buildship-dev mailing list. (Is that list dead?)

I’m responsible for several Gradle builds that lean heavily on the more complex features of Gradle: attribute schema extension, variant selection, additional test suites, additional source sets, custom plugins etc. I’m currently faced with the prospect of a mandated shift to Eclipse (or VSCode wrapping Eclipse) as a developer platform/IDE and I’m trying to get a handle on the scale and nature of my problems. To that end I’m trying to define or understand:

  1. What are the current limits placed on Gradle builds by the ability of Buildship to translate the Gradle build to the Eclipse Project Model.
  2. What are the theoretical limits placed on Gradle builds by the Eclipse Project Model itself.
  3. How fast is (or can) Buildship close the gap between these two limits?

Any insights on these questions would be greatly appreciated, and massively help me understand the scale of the rework required in my build-systems, and potentially in my product delivery.

Thanks,

Chris