Well, keeping track of the actual dependencies was one of the reasons, however, the main reason was the underlying dependency management done by Gradle (via Maven repositories) had to be 'turned off' due to incompatible versions in other dependencies or their downstream dependencies. There were dependency versions included in the product which were not compatible with other dependency versions or their downstream libraries. I believe the task here is to go through the dependencies and verify each of their downstream dependencies are compatible.
Some of this work has been started, like moving to a newer version of JLine which would allow to use another version of the Spring Framework, but I have not looked into all known issues. This is loosely related to GEODE-27. --Mark On Mon, Dec 21, 2015 at 3:04 PM, Jens Deppe <[email protected]> wrote: > I see that we're setting transitive to false for all dependencies. I guess > that was done so that we're explicit about what is absolutely required as a > dependency for GemFire. > > I'd like to propose we relax that for test dependencies. I really don't see > the need to track every transitive dependency that is used for testing. > > Thoughts? Comments? > > --Jens >
