Implement the skeleton of an android content shell.

content/android/java/content.xml

Index: content/android/java/content.xml
diff --git a/content/android/java/content.xml b/content/android/java/content.xml
new file mode 100644
index 0000000000000000000000000000000000000000..a00a4e564565e80ca852db7c4e466caa8f56acdd
--- /dev/null
+++ b/content/android/java/content.xml
@@ -0,0 +1,61 @@
+<!-- Copyright (c) 2012 The Chromium Authors. All rights reserved.

[jam, 2012/04/19 21:56:26]

why content/android? we don't have content/win or content/mac or content/linux

[Ted C, 2012/04/20 01:14:14]

I'll let Grace comment on this one as I'm just following the convention we
decided downstream, and she will be better able to explain why.

[klobag.chromium, 2012/04/20 01:32:25]

When we start to upstream Java files, we came up with the conclusion that we
will put all the Java files under android in each top directory. The top
directory is defined where the *.gyp is. The Java files will keep the sub
directory structure. In this case, all Java files for content will be under
content/android.

[jam, 2012/04/20 16:15:28]

as someone not familiar with android development, can you explain to me what
these java files are used for? are they used when building an application over
content? i.e. will every android embedder of content require these files, or
just content_shell and chrome on android which is in your own repo?

[klobag.chromium, 2012/04/20 17:13:57]

These Java files will be shared by any Android embedder, which includes
content_shell, Chrome for Android and tests.

On 2012/04/20 16:15:28, John Abd-El-Malek wrote:

[jam, 2012/04/20 21:40:03]

I see. In that case, how about content/public/android? chrome right now can only
access content/public and content/test. Since content/public is what embedders
are supposed to use, it seems that these files belong there?

+
+     Use of this source code is governed by a BSD-style license that can be
+     found in the LICENSE file.
+-->
+<project name="Content" default="dist" basedir=".">
+  <description>
+    building content java source code with ant
+  </description>
+  <!-- set global properties for this build -->
+  <property environment="env"/>
+  <property name="sdk.dir" location="${env.ANDROID_SDK_ROOT}"/>
+  <property name="sdk.version" value="${env.ANDROID_SDK_VERSION}"/>
+  <property name="src" location="."/>
+  <property name="out.dir" location="${PRODUCT_DIR}"/>
+  <property name="classes.dir" location="${out.dir}/java/${PACKAGE_NAME}"/>
+  <!-- TODO(tedchoc): Move out of the main out/ dir ... needs to sync with
+       java.gypi output -->
+  <property name="jar.dir" location="${out.dir}"/>
+
+  <condition property="location.base"
+             value="${sdk.dir}"
+             else="${sdk.dir}/platforms/android-${sdk.version}">
+    <isset property="env.ANDROID_BUILD_TOP"/>
+  </condition>
+
+  <target name="init">
+    <!-- Create the time stamp -->
+    <tstamp/>
+    <!-- Create the build directory structure used by compile -->
+    <mkdir dir="${out.dir}"/>
+  </target>
+
+  <target name="compile" depends="init"
+          description="compile the source " >
+    <!-- Create the classes output directory -->
+    <mkdir dir="${classes.dir}"/>
+
+    <!-- Compile the java code from ${src} into ${classes.dir} -->
+    <javac srcdir="${src}" destdir="${classes.dir}">
+      <classpath>
+        <path location="${location.base}/android.jar"/>
+      </classpath>
+    </javac>
+  </target>
+
+  <target name="dist" depends="compile"
+          description="generate the distribution" >
+    <!-- Create the distribution directory -->
+    <mkdir dir="${jar.dir}"/>
+
+    <!-- Put everything in ${classes.dir} into the chromium_content.jar file -->
+    <jar jarfile="${jar.dir}/chromium_${PACKAGE_NAME}.jar" basedir="${classes.dir}"/>
+  </target>
+
+  <target name="clean" description="clean up" >
+    <!-- Delete the generated content -->
+    <delete dir="${classes.dir}"/>
+    <delete file="${jar.dir}/chromium_${PACKAGE_NAME}.jar"/>
+  </target>
+</project>