Hey, - using withType requires me to know the fully qualified name of the class. - using withType requires me to import the class (extra statement in the build script) or refer via fqn, both don't look good. It's not painful for built-in Gradle classes (because they are implicitly imported) but many times I need to work with my custom plugins or 3d party types. - as a plugin author, I'd like the fqn of the plugin class to be 'internal' so that I can refactor it freely, rename, change packages at will.
Cheers! On Thu, Mar 13, 2014 at 7:08 PM, Rene Groeschke <gra...@breskeby.com> wrote: > Can you explain a bit the usecase? why is PluginContainer.withType not > enough? > > cheers, > René > > > Szczepan Faber <szczepan.fa...@gradleware.com> > 13 Mar 2014 15:15 > Hey guys, > > Are there any objections to adding PluginContainer.withId(String id) > method? > > Cheers! > -- > Szczepan Faber > Principal engineer@gradle; Founder@mockito > > -- Szczepan Faber Principal engineer@gradle; Founder@mockito
<<inline: compose-unknown-contact.jpg>>
