Hi. Are there any plans to allow the following: 1. be able to define additional classpath per task, as opposed to the whole project 2. be able to define additional classpath / dependencies per plugin? jetty plugin comes to mind, as it uses a fixed jetty version (6.x currently)
Maven allows classpath per plugin (which roughly corresponds to task in gradle) - do you plan on something similar? If not, what would be the way to, say, upgrade the jetty plugin to use another jetty instance, apart from messing around with gradle distribution (which is a hack, and not really usable with gradle wrapper, which I love).
What would be the way for multiple plugins to use some library in different versions? I guess a plugin would need to define a custom configuration and use just it, but this seems a workaround as well.