[Third Party] Add sqlite4java to Chromium.

third_party/sqlite4java/BUILD.gn

+# Copyright 2016 The Chromium Authors. All rights reserved.
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+
+import("//build/config/android/rules.gni")
+
+java_prebuilt("sqlite4java_java") {
+  testonly = true
+  jar_path = "lib/sqlite4java-0.282.jar"

[the real yoland, 2016/06/22 21:32:26]

Comments on why linux, mac, window subdirectories and jar files are needed?

+}

[mikecase (-- gone --), 2016/06/22 21:42:50]

Just fyi, the reason none of the .so/.dll/.jnilib are here in the build file is
kind of Robolectric specific. Robolectric look for these libraries in a very
specific path on the classpath.

See:
https://github.com/robolectric/robolectric/blob/master/robolectric-shadows/sh...

For example, it looks for "linux-x86/libsqlite4java.so" on the classpath. If I
recall, just having libsqlite4java.so on the classpath isn't sufficient; it has
to be in the specific directory robolectric is looking for it.

Two options: (1) Modify the Robolectric source code to look for the libraries
where GN adds them to the classpath. (2 [what I am doing now]) Package these
libraries in the Robolectric jar in the path Robolectric expects.

[jbudorick, 2016/06/27 13:31:17]

Can we do 2 in the short term w/ a plan of doing 1 in the long term? This seems
... pretty nasty.

[mikecase (-- gone --), 2016/06/27 17:17:31]

That sounds fine with me. There is another classpath related thing I want to fix
for Robolectric in chromium. That one being that the jars it loads at runtime
need to also have very specific names. It is why these targets....

https://cs.chromium.org/chromium/src/third_party/robolectric/BUILD.gn?sq=pack...

...have ugly names like "json-20080701" and "android-all-4.3_r2-robolectric-0".
This is so GN creates the jars with the names Robolectric expects. I'll work on
cleaning up both of these things once everything has landed.