This splits the library into three Gradle modules:
core - volley core + toolbox
cronet - CronetHttpStack
testing - common testing code
The primary purpose is to split out CronetHttpStack into its own Maven
artifact, com.android.volley:volley-cronet, to prevent applications
which aren't using it from having to either suppress Proguard/D8
warnings or pull in the unnecessary dependency.
The testing module is needed to share TestRequest between unit tests
in both core and cronet. It is not published to Maven.
This PR also removes support for the build.gradle/rules.gradle split
which allowed Gradle projects to depend on Volley by source and
specify their own SDK settings. This is no longer worth supporting,
and any client that wishes to depend on Volley via Gradle should do
so via published Maven artifacts instead.
This splits the library into three Gradle modules:
The primary purpose is to split out CronetHttpStack into its own Maven artifact, com.android.volley:volley-cronet, to prevent applications which aren't using it from having to either suppress Proguard/D8 warnings or pull in the unnecessary dependency.
The testing module is needed to share TestRequest between unit tests in both core and cronet. It is not published to Maven.
This PR also removes support for the build.gradle/rules.gradle split which allowed Gradle projects to depend on Volley by source and specify their own SDK settings. This is no longer worth supporting, and any client that wishes to depend on Volley via Gradle should do so via published Maven artifacts instead.
See #412