A problem I'm having with @kobalt is that it likel...
# kobalt
a
A problem I'm having with @kobalt is that it likely is somewhat of a "targeted at gradle past" instead of "gradle future" ... Gradle will do a big change soon for dependency management, and with plugins like Prezi/Pride multi-project scenarios are better handled although klunky in Gradle. I'd like to plugin our brikk dependency system and do the multi-project work for kobalt. To do that, this part of the system has to be pluggable and allow delegation to your maven resolver only when desired (likely not).