I have a Gradle build that uses a custom plugin which makes heavy use of attributes and variant resolution to implement a "partial shading" scheme. At the command line everything works perfectly, and in IntelliJ everything also works great. Downstream projects correctly pick all the right configurations when resolving things for compile, runtime etc... I'm now faced with the possibility of a mandate to move to Eclipse, and I'm running in to lots of issues with Eclipse not being able to pierce the shading veil. Does anyone know how Buildship forms the various Eclipse classpaths and whether I have any hope of making things work when my outgoingVariants are not formed by, or named the same as the ones created by the stock Gradle plugins?