I'm trying to gain clarity in to the Gradle IDE support situation for Eclipse and VSCode. I have a fairly complex Gradle build that makes use of things like: • build-logic • extensive custom plugins and conventions • attribute schema extension • additional test suites (including without java plugin) • nodejs plugins (ysb33r) • attribute aware variant selection This all functions perfectly well in IntelliJ, but falls flat on it's face in both Eclipse and VSCode (when using the default Buildship/Eclipse extensions). What I'm trying to get a good understanding of is: 1. Where are the current bounds on a Gradle build imposed by Eclipse/Buildship? What features will/won't work. 2. What are the theoretical bounds on the same? What can never work in this area? I need to be able to understand how much of a reengineering of the build system will be necessary to get things functional so that I can estimate the task, and establish a plan of attack (potentially including fundamental shifts to our product delivery and integration testing). (apologies for the direct invokes of the major buildship contributors: @Donát Csikós @Etienne Studer @oehme)