Maybe I didn’t communicate this correctly. There’s no problem with resolving transitive dependencies of plugins. The issue I am referring to is the fact that the Jetty plugin gets its dependencies provides by Gradle core (lib/plugins). In case you’d move the Tomcat plugin into Gradle Phil would like its dependencies to be provided by Gradle as well and not declaratively by a custom configuration. Jetty’s dependencies would clash with the ones needed by the Tomcat plugin e.g. the JSP API version.
In terms of Gradle plugins I am referring to feature requests that I would like to see e.g. that plugins should declare its dependencies in a descriptor like Grails does it for example. It would be great if the user wouldn’t have to declare this if they don’t want to. I will put together my ideas and thoughts in a new post soon.