Add skeleton of content shell for android.

content/shell/android/java/org/chromium/content_shell/ContentShellActivity.java

+// Copyright (c) 2012 The Chromium Authors. All rights reserved.

[Ted C, 2012/03/27 17:16:23]

I think to make this easier to match other android applications, the path should
be include src before the org.

The typical layout I've seen is:

AndroidManifest.xml
src -> path/to/source
res -> drawables/layouts/etc...needed by the application

[Satish, 2012/03/27 20:15:28]

Agree on the general dir structure. 'src' has a predefined meaning in chromium
and webkit because of the 'src' and 'include' split where .cc files go under src
and .h under include. So we seem to be going with 'java' instead (e.g.
base/android/java/org/... )

[Ted C, 2012/03/27 20:33:02]

I will argue that is not a good precedence.  All Android apps I've seen follow
the directory structure defined below, and I think we will be in a much better
shape if we do the same.

http://developer.android.com/guide/developing/projects/index.html

I think having the simple /java directory is good for things we will be making
.jars out of, but APKs should follow the android guidelines.

I'll cc Grace on this and hopefully she can comment as to whether this is
necessary.  Maybe, this isn't as big of a deal as it seems to me.

+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+package org.chromium.content_shell;
+
+import android.app.Activity;
+import android.os.Bundle;
+import android.util.Log;
+
+public class ContentShellActivity extends Activity {

[Ted C, 2012/03/27 17:16:23]

Class level javadoc...let's start this project out on a good note :-)

[Satish, 2012/03/27 20:15:28]

Done.

+    private final String TAG = "ContentShellActivity";
+
+    @Override
+    public void onCreate(Bundle savedInstanceState) {
+        super.onCreate(savedInstanceState);
+        Log.i(TAG, "Content shell started");
+    }
+}