Now that the Mobile SDK v1.0.0 is moved over to a Gradle based build system, has Oculus considered setting up a Maven or Ivy repository to store VrApi, VrAppSupport, and the other pre-built libraries?
Currently the build system expects everything to be under the root SDK folder, which is great for sample code. But assuming the developers want to keep their projects under their own hierarchies, it is currently a bit cumbersome to include the OVR SDK libraries from a separate hierarchy. Copying library directories from the SDK directory to your project/workspace directory breaks ownership encapsulation and makes it more difficult to update the SDK later. Symlinks are a bit touchy when it comes to source control systems. Hard-coding local library paths in the gradle settings is possible, but not the cleanest approach. Gradle seems to be designed around the Maven/Ivy repository paradigm, so has there been talk at Oculus about setting one up?
