Other builds might use managed dependencies as much as possible, but occasionally fall back to static management for pragmatic reasons. For example, if you need to hack an old, unsupported vendor JAR at the bytecode level, or otherwise have a highly custom build of some external module, it might make more sense to control that JAR with your source code rather than publish it to a binary repository. This scenario is most likely when you don’t have your own internal binary repository and module publishing mechanism established.
Have an internal binary repository and module publishing mechanism
Share this highlighthttp://www.safaribooksonline.com/a/gradle-beyond-the/772/