Remove {base,net}_java dependencies from GYP client targets on Android.

content/content.gyp

Index: content/content.gyp
diff --git a/content/content.gyp b/content/content.gyp
index 41b1c0294687f4cdc8f337924d1a808d667607ae..f4883eac19f78f7f1a88ca7787ab27f4ea394766 100644
--- a/content/content.gyp
+++ b/content/content.gyp
@@ -243,15 +243,10 @@
          'target_name': 'content_java',
          'type': 'none',
          'dependencies': [
-           '../base/base.gyp:base_java',

[cjhopman, 2012/09/06 20:29:25]

I believe that the dependency on base_java here was due to the fact that
content_java depends directly on base_java. By removing it, you still inherit
the dependent settings through net, but lose the documentation aspect that this
depends directly on base. I would specify the dependency here (unless
content_java doesn't actually depend directly on base_java).

[Philippe, 2012/09/07 09:45:57]

These changes were pretty random indeed. The code under
content/public/android/java does depend explicitly on base so this dependency
should be kept.

-           '../net/net.gyp:net_java',
+           '../net/net.gyp:net',
            'common_aidl',
            'content_common',
          ],
-         'export_dependent_settings': [
-           '../base/base.gyp:base_java',
-           '../net/net.gyp:net_java',

[cjhopman, 2012/09/06 20:29:25]

Removing these exports would make an apk that specifies a dependency on
content_java (or content, now) but not the others break as it would no longer
inherit the input_jars_paths from base and net. There probably aren't any such
targets currently.

[Philippe, 2012/09/07 09:45:57]

I don't think I had strong reasons to do this. I finally kept it (after I did
s/_java//).

-         ],
          'variables': {
            'package_name': 'content',
            'java_in_dir': '../content/public/android/java',