Additional content massaging based on feedback received.
diff --git a/pdk/docs/source/building-dream.jd b/pdk/docs/source/building-dream.jd
index f5472ce..89392fd 100644
--- a/pdk/docs/source/building-dream.jd
+++ b/pdk/docs/source/building-dream.jd
@@ -1,6 +1,8 @@
-page.title=Building for ADP1
+page.title=Building for an Android Dev Phone
doc.type=source
@jd:body
+<p><i>The information on this page is a bit out of date. We'll update this
+page as soon as we can.</i></p>
<div>The basic manifest for cupcake (and above) defines which projects are
needed to do a generic build for the emulator or for unlocked Dream devices
(e.g. the Android Dev Phone 1). You need to have an appropriate device running
diff --git a/pdk/docs/source/code-style.jd b/pdk/docs/source/code-style.jd
index 3122ea8..8b5946e 100644
--- a/pdk/docs/source/code-style.jd
+++ b/pdk/docs/source/code-style.jd
@@ -2,12 +2,11 @@
doc.type=source
@jd:body
<div>
-<h1>Android Code Style Rules</h1>
-<p>The rules below are not guidelines or recommendations, but strict rules.<b>You may not disregard the rules we list below</b>
-except as approved on a need-to-use basis.
+<p>The rules below are not guidelines or recommendations, but strict rules.
+Contributions to Android generally <b>will not be accepted if they do not
+adhere to these rules.</b>
</p>
-<p>Not all existing code follows these rules, but all new code is expected to.
-</p>
+<p>Not all existing code follows these rules, but all new code is expected to.</p>
<h1><a>Java Language Rules</a>
</h1>
<p>We follow standard Java coding conventions. We add a few rules:
diff --git a/pdk/docs/source/documentation.jd b/pdk/docs/source/documentation.jd
deleted file mode 100644
index 4eae071..0000000
--- a/pdk/docs/source/documentation.jd
+++ /dev/null
@@ -1,54 +0,0 @@
-page.title=Documentation Resources
-doc.type=source
-@jd:body
-<div><p>
- As this page grows, it will include resources for wireless operators and handset manufacturers as well as for platform developers.<br></p>
-<h3>
-Resources for platform developers
- </h3>
-
- Google I/O videos:<br><ul><li><a href="http://sites.google.com/site/io/an-introduction-to-android">Introduction to Android</a>
-<img src="{@docRoot}images/documentation-0.png">
-<br></li>
-<li><a href="http://sites.google.com/site/io/anatomy--physiology-of-an-android">Anatomy Physiology of an Android</a>
-<img src="{@docRoot}images/documentation-0.png">
-</li>
-<li><a href="http://sites.google.com/site/io/inside-the-android-application-framework">Inside the Android Application Framework</a>
-<img src="{@docRoot}images/documentation-0.png">
-</li>
-<li><a href="http://sites.google.com/site/io/dalvik-vm-internals">Dalvik VM Internals</a>
-<img src="{@docRoot}images/documentation-0.png">
-</li>
-</ul>
-
- Getting started with the Android source code:<br><ul><li><a href="http://source.android.com/download">Get source</a>
-</li>
-<li><a href="http://source.android.com/submit-patches/code-style-guide">Code Style Guide</a>
-<br></li>
-</ul>
-
- Repo and Git resources:<br><ul><li><a href="http://source.android.com/download/using-repo#TOC-Git-and-Repo-cheatsheet">Git and Repo cheat sheet</a>
-</li>
-<li><a href="http://source.android.com/download/using-repo">Using Repo and Git <br></a>
-</li>
-<li>
- The <a href="http://book.git-scm.com/">Git Community Book</a>
-<img src="{@docRoot}images/documentation-0.png">
-maintained by Scott Chacon <br></li>
-<li><a href="http://git.or.cz/gitwiki/FrontPage">GitWiki</a>
-<img src="{@docRoot}images/documentation-0.png">
-</li>
-<li><a href="http://www.kernel.org/pub/software/scm/git/docs/">Git Manual Page</a>
-<img src="{@docRoot}images/documentation-0.png">
-</li>
-<li><a href="http://www.gitcasts.com/">GitCasts</a>
-<img src="{@docRoot}images/documentation-0.png">
-(Git how-to videos)
- </li>
-</ul>
-
- Documentation on specific tasks:<br><ul><li><a href="http://source.android.com/documentation/building-for-dream">Building for Dream</a>
-(Android Developer Phone 1)
- </li>
-</ul>
-</div>
diff --git a/pdk/docs/source/git-repo.jd b/pdk/docs/source/git-repo.jd
index 97bd2ea..ac7fd37 100644
--- a/pdk/docs/source/git-repo.jd
+++ b/pdk/docs/source/git-repo.jd
@@ -19,11 +19,15 @@
One of the challenges in setting up the Android project was figuring out how to best support the outside community--from the hobbiest community to large OEMs building mass-market consumer devices. We wanted components to be replaceable, and we wanted interesting components to be able to grow a life of their own outside of Android. We first chose a distributed revision control system, then further narrowed it down to Git.<br><h3>
Already a Git user?
</h3>
-In most situations, you can use Git instead of Repo, or mix Repo and Git commands to form complex commands. Using Repo for basic across-network operations will make your work much simpler, however. For more information about Git, see the list of resources on our <a href="http://sites.google.com/a/android.com/opensource/documentation">Documentation</a>
-page.<br></div>
+In most situations, you can use Git instead of Repo, or mix Repo and Git
+commands to form complex commands. Using Repo for basic across-network
+operations will make your work much simpler, however.
+<br></div>
<div><div><h2>
Task reference <br></h2>
-The task list below shows a summary of how to do common Repo and Git tasks. For complete quick-start information and examples, see <a href="http://sites.google.com/a/android.com/opensource/download">Get source</a>
+The task list below shows a summary of how to do common Repo and Git tasks.
+For complete quick-start information and examples, see <a
+href="{@docRoot}source/download.html">Get source</a>
.
<h3>
Installing Repo <br></h3>
@@ -33,8 +37,9 @@
$ repo init-u git://android.git.kernel.org/platform/manifest.git <br><br><h3>
Synchronizing your client
</h3>
-To synchronize the files for all available <a href="http://sites.google.com/a/android.com/opensource/projects">projects</a>
-:<br>$ repo sync <br><br>To synchronize the files for selected projects:<br>$ repo sync <i>project1 project2 ...</i>
+To synchronize the files for all available projects:<br>$ repo sync <br><br>To
+synchronize the files for selected projects:<br>$ repo sync <i>project1
+project2 ...</i>
<i><br></i>
<br><h3>
Why use topic branches?
@@ -269,6 +274,40 @@
<div><img src="{@docRoot}images/git-repo-1.png">
</div>
+
+<!--
+<h2>Additional Resources</h2>
+<h3>Resources for platform developers</h3>
+Google I/O videos:
+<ul>
+ <li><a href="http://sites.google.com/site/io/an-introduction-to-android">Introduction to Android</a></li>
+ <li><a href="http://sites.google.com/site/io/anatomy-physiology-of-an-android">Anatomy Physiology of an Android</a></li>
+ <li><a href="http://sites.google.com/site/io/inside-the-android-application-framework">Inside the Android Application Framework</a></li>
+ <li><a href="http://sites.google.com/site/io/dalvik-vm-internals">Dalvik VM Internals</a></li>
+</ul>
+
+Getting started with the Android source code:
+<ul>
+ <li><a href="http://source.android.com/download">Get source</a></li>
+ <li><a href="http://source.android.com/submit-patches/code-style-guide">Code Style Guide</a></li>
+</ul>
+
+Repo and Git resources:
+<ul>
+ <li><a href="http://source.android.com/download/using-repo#TOC-Git-and-Repo-cheatsheet">Git and Repo cheat sheet</a></li>
+ <li><a href="http://source.android.com/download/using-repo">Using Repo and Git</a></li>
+ <li>The <a href="http://book.git-scm.com/">Git Community Book</a> maintained by Scott Chacon</li>
+ <li><a href="http://git.or.cz/gitwiki/FrontPage">GitWiki</a></li>
+ <li><a href="http://www.kernel.org/pub/software/scm/git/docs/">Git Manual Page</a></li>
+ <li><a href="http://www.gitcasts.com/">GitCasts</a> (Git how-to videos)</li>
+</ul>
+
+Documentation on specific tasks:
+<ul>
+ <li><a href="http://source.android.com/documentation/building-for-dream">Building for an Android Developer Phone</a></li>
+</ul>
+-->
+
<h2>
<b>Terminology</b>
</h2>
diff --git a/pdk/docs/source/index.jd b/pdk/docs/source/index.jd
index 4960e30..230a0b3 100644
--- a/pdk/docs/source/index.jd
+++ b/pdk/docs/source/index.jd
@@ -3,9 +3,9 @@
@jd:body
<div>
<p>Thanks for your interest in Android! Here are some ways you can get involved
-and help us improve Android. For background on the Android project and our
-goals, check out <a href="{@docRoot}about/philosophy.html">Our
-Philosophy</a>.</p>
+and help Google improve Android. For background on the Android project and our
+goals, check out the <a href="{@docRoot}about/philosophy.html">Project
+Philosophy page</a>.</p>
<h2>Report Bugs</h2>
<p>One of the easiest and most effective ways you can help improve Android is
diff --git a/pdk/docs/source/licenses.jd b/pdk/docs/source/licenses.jd
index 0d2cf2e..846a92a 100644
--- a/pdk/docs/source/licenses.jd
+++ b/pdk/docs/source/licenses.jd
@@ -65,18 +65,16 @@
(For instance, it's difficult for a user to replace a library on read-only
flash storage.)</li>
<li>LGPL requires allowance of customer modification and reverse
-engineering for debugging those modifications. Most app producers do
-want to have to be bound by these terms, and the more userspace libs
-that are LGPL, the more they would have to be to use Android
-userspace.</li>
+engineering for debugging those modifications. Most device makers do
+not want to have to be bound by these terms, so to minimize the burden on
+these companies we minimize usage of LGPL software in userspace.</li>
<li>Historically, LGPL libraries have been the source of a large number
of compliance problems for downstream device makers and application
-developers (due to ignorance and disbelief, usually). Education is
-slow going, sadly. Part of android being successful as a platform is
-that we want to make it easy for our device makers to comply with the
-licenses in Android. Given the difficulties with complying with LGPL
-in the past, it is easiest to simply not use LGPL libraries if we can
-avoid it.</li>
+developers. Educating engineers on these issues is difficult and slow-going,
+unfortunately. It's critical to Android's success that it be as easy as
+possible for device makers to comply with the licenses. Given the
+difficulties with complying with LGPL in the past, it is most prudent to
+simply not use LGPL libraries if we can avoid it.</li>
</ol>
<p>The issues discussed above are our reasons for preferring ASL2.0 for
our own code. They aren't criticisms of LGPL or other licenses. We do
diff --git a/pdk/docs/source/life-of-a-bug.jd b/pdk/docs/source/life-of-a-bug.jd
index 1eb1bc4..1d58ae1 100644
--- a/pdk/docs/source/life-of-a-bug.jd
+++ b/pdk/docs/source/life-of-a-bug.jd
@@ -53,8 +53,10 @@
to a contributor.</p></li>
<li><b>Reviewed</b><p>Like <code>Unassigned</code>, but the issue
represented is being tracked in a separate bug database. For example, the bug
-might have been reported via an AOSP member's internal bug-tracking system,
-which is considered the "master" copy.</p></li>
+might have been reported via an internal bug-tracking system,
+which is considered the "master" copy. (For instance, Google maintains one
+such private issue tracker, intended primarily for bugs which contain
+sensitive information which can't be revealed publicly.)</p></li>
<li><b>Assigned</b><li>Like <code>Unassigned</code>, but the bug has been
actually assigned to a specific contributor to fix.</p></li>
</ul>
@@ -120,7 +122,7 @@
actually multiple issue trackers for Android-related issues. The <a
href="http://code.google.com/p/android/issues/list">Google Code Project
Hosting Issue Tracker</a> is the <b>only</b> official public issue tracker; however,
-many of the AOSP Member organizations maintain their own, as do most OEMs. We
-try to keep the public issue tracker in sync with private issue trackers
+Google also maintains a private issue tracker, own, as do most OEMs. We try to
+keep the public issue tracker in sync with private issue trackers
wherever possible, but in cases where confidential information and security
issues are involved, this isn't always possible.</p>
diff --git a/pdk/docs/source/overview.jd b/pdk/docs/source/overview.jd
index 9874b4b..2763c52 100644
--- a/pdk/docs/source/overview.jd
+++ b/pdk/docs/source/overview.jd
@@ -9,6 +9,11 @@
the source code onto your local machine. You can use <code>repo init -u
git://android.git.kernel.org/platform/manifest.git -b android-1.6</code>
to download the source code for Android 1.6.</p>
+<p><i>Note: platform overview information for Android 2.x has not yet been
+published, since the <a
+href="{@docRoot}compatibility/index.html">Compatibility Program</a> for
+Android 2.x has not yet launched. When the Compatibilty Definition Document
+for 2.x is released, this page will be updated to match.</i></p>
<p>Information about older Android releases is also available:<ul>
<li><a href="{@docRoot}source/overview-1.5.html">Android 1.5 Platform Overview</a></li>
<li><a href="{@docRoot}source/overview-1.0.html">Android 1.0 Platform Overview</a></li>
diff --git a/pdk/docs/source/report-bugs.jd b/pdk/docs/source/report-bugs.jd
index e89fbbe..138080d 100644
--- a/pdk/docs/source/report-bugs.jd
+++ b/pdk/docs/source/report-bugs.jd
@@ -21,13 +21,16 @@
templates:<ul>
<li><a
href="http://code.google.com/p/android/issues/entry?template=User%20bug%20report">Bugs
- in your Device (for users)</a></li>
+ in your Device (for users)</a> - use this if you want to report a bug in a
+ device you own</li>
<li><a
href="http://code.google.com/p/android/issues/entry?template=Developer%20bug%20report">Bugs
- in the Software (for developers)</a></li>
+ in the Software (for developers)</a> - use this if you found a bug in the
+ course of developing an app</li>
<li><a
href="http://code.google.com/p/android/issues/entry?template=Feature%20request">Request
- a New Feature</a></li>
+ a New Feature</a> - use this for a feature you'd like to see in a future
+ verison</li>
</ul></li>
</ol>
<p>Please note that we can't guarantee that any particular bug can be fixed in
@@ -54,6 +57,11 @@
Observed results:
See above.
</pre>
+<p>This is a poor bug report because it doesn't provide any context for the
+issue; is it a problem in the Dalvik virtual machine, the core framework, or
+something else? It also doesn't provide any code or hint on how to reproduce
+it. In other words, this bug report doesn't provide enough information for
+anyone to take action on, so it would be ignored.</p>
<h3>A Good Bug Report</h3>
<pre>
Title: Stepping over "Object o = null" causes Eclipse "Internal Error"
diff --git a/pdk/docs/source/roles.jd b/pdk/docs/source/roles.jd
index 2b4a721..451c821 100644
--- a/pdk/docs/source/roles.jd
+++ b/pdk/docs/source/roles.jd
@@ -1,12 +1,12 @@
page.title=People and Roles
doc.type=source
@jd:body
-<div>
<p>The Android Open Source Project (AOSP) includes individuals working in a variety
of roles. As noted in <a href="{@docRoot}about/philosophy.html">Our
-Philosophy</a>, the core AOSP members operate the Android product management
-and engineering process. This page describes these roles in a bit more
-detail.</p>
+Philosophy</a>, Google is responsible for Android product management
+and the engineering process for the core framework and platform; however,
+the project considers contributions from any source, not just Google. This
+page describes the kinds of roles that interested parties can take on.</p>
<p>Anyone who is interested in exploring and contributing to Android can use the
Android Open Source Project resources. Anyone can join the mailing lists, ask
questions, contribute patches, report bugs, look at submitted patches, and use
@@ -15,10 +15,10 @@
<h2>Contributor</h2>
<p>A "Contributor" is anyone making contributions to the AOSP source code,
-including both employees or other affiliates of an AOSP Member, as well as
+including both employees of Google or other companies, as well as
external developers who are contributing to Android on their own behalf.
-There is no distinction between Contributors who are affiliated with an AOSP
-Member, and those who are not: all engineers use the same git/gerrit tools,
+There is no distinction between Contributors who are employed by
+Google, and those who are not: all engineers use the same git/gerrit tools,
follow the same code review process, and are subject to the same requirements
on code style and so on.</p>
<p/>
@@ -26,9 +26,9 @@
<h2>Developer</h2>
<p>A "Developer" is an engineer writing applications that run on Android
devices. There is, of course, no difference in skillset between a "Developer"
-and a "Contributor"; we simply use "Developer" to help identify our audience.
+and a "Contributor"; AOSP simply uses "Developer" to help identify our audience.
Since the key purpose of Android is to cultivate an open development platform,
-"Developers" are one of the key customers of the Android project. As such, we
+"Developers" are one of the key customers of the Android platform. As such, we
talk about them a lot, though this isn't technically a separate role in the
AOSP <i>per se.</i></p>
<p/>
@@ -44,18 +44,17 @@
"Approvers" are experienced members of the project who have demonstrated their
design skills and have made significant technical contributions to the
project. In the code-review process, an Approver decides whether to include or
-exclude a change. Project Leads (typically employed by an AOSP Member) choose
+exclude a change. Project Leads (who are typically employed by Google) choose
the Approvers, sometimes promoting to this position Verifiers who have
demonstrated their expertise within a specific project.</p>
<p/>
<h2>Project Leads</h2>
<p>Android consists of a number of sub-projects; you can see these in the git
-repository, as individual .git files. The AOSP Members generally assign tech
-leads or product leads who oversee the engineering for individual Android
-projects. Typically these tech leads will be employees of an AOSP Member
-company. A Project Lead for an individual project is responsible for the
-following:</p>
+repository, as individual .git files. Tech Leads are senior Contributors who
+oversee the engineering for individual Android projects. Typically these tech
+leads will be Google employees. A Project Lead for an individual project is
+responsible for the following:</p>
<ul>
<li>Lead all technical aspects of the project; for example, the project
roadmap, development, release cycles, versioning, and QA.</li>
@@ -72,4 +71,3 @@
<li>Be the public face for the project and the go-to person for questions
related to the project.</li>
</ul>
-</div>
diff --git a/pdk/docs/source/source_toc.cs b/pdk/docs/source/source_toc.cs
index 1531aff..09c20a6 100644
--- a/pdk/docs/source/source_toc.cs
+++ b/pdk/docs/source/source_toc.cs
@@ -8,9 +8,10 @@
<li><h2>The Project</h2><ul>
<li><a href="<?cs var:toroot ?>source/roles.html">People and Roles</a></li>
<li><a href="<?cs var:toroot ?>source/licenses.html">Licensing Information</a></li>
- <li><a href="http://android.git.kernel.org/">Browse Source</a></li>
+ <li><a href="http://android.git.kernel.org/">Browse Source</a> <span style="font-size: 75%; font-variant: small-caps">[off-site]</span></li>
<li><a href="<?cs var:toroot ?>source/overview.html">Platform Overview</a></li>
<li><a href="<?cs var:toroot ?>source/life-of-a-bug.html">Life of a Bug</a></li>
+ <li><a href="<?cs var:toroot ?>faqs.html#aosp">FAQs</a></li>
</ul>
<li><h2>Getting Started</h2><ul>
@@ -18,7 +19,7 @@
<li><a href="<?cs var:toroot ?>source/git-repo.html">Using git and repo</a></li>
<li><a href="<?cs var:toroot ?>source/using-eclipse.html">Using Eclipse</a></li>
<li><a href="<?cs var:toroot ?>source/code-style.html">Code Style</a></li>
- <li><a href="<?cs var:toroot ?>source/building-dream.html">Building for ADP1</a></li>
+ <li><a href="<?cs var:toroot ?>source/building-dream.html">Building for an ADP</a></li>
</ul>
<li><h2>Contributing</h2><ul>
diff --git a/pdk/docs/source/submit-patches.jd b/pdk/docs/source/submit-patches.jd
index 880a682..2b7bae1 100644
--- a/pdk/docs/source/submit-patches.jd
+++ b/pdk/docs/source/submit-patches.jd
@@ -8,13 +8,10 @@
see <a href="{@docRoot}source/download.html">Get source</a>
.<br><br>Other recommended reading:<br><ul><li>For an overview of the code
contribution and review process, see <a
-href="{@docRoot}source/submit-patches.html">Workflow</a>
-.</li>
-<li>For details about Repo, see <a href="{@docRoot}source/git-repo.html">Using Repo and Git</a>
-.<br></li>
+href="{@docRoot}source/life-of-a-patch.html">Life of a Patch</a>.</li>
+<li>For details about Repo, see <a href="{@docRoot}source/git-repo.html">Using Repo and Git</a>.<br></li>
<li>For information about the different roles you can play within the Android
-Open Source community, see <a href="{@docRoot}source/roles.html">Project roles</a>
-.</li>
+Open Source community, see <a href="{@docRoot}source/roles.html">Project roles</a>.</li>
<li>If you plan to contribute code to the Android platform, be sure to read
the <a href="{@docRoot}source/licenses.html">AOSP's licensing information</a>.</li>
</ul>
@@ -40,16 +37,14 @@
</ol>
You can track your uploaded changes using the Gerrit code-review tool. When it's time to work on the code again, run repo sync, then go back to step 1 above and start another topic branch.<br><br>The steps will not always come in the order shown--for example, you might run git diff at several points in the process.<br><br><h3>
Starting a topic branch</h3>
-Start a topic branch called default in your local work environment:<br><br>$ repo start default <br><br>For more about topic branches, see <a href="{@docRoot}source/git-repo.html">Using Repo and Git</a>
-.<br><h3>
+Start a topic branch called default in your local work environment:<br><br>$ repo start default <br><br>For more about topic branches, see <a href="{@docRoot}source/git-repo.html">Using Repo and Git</a>.<br><h3>
Editing the files</h3>
You do not need to check files out before working on them. Edit the files using vim, emacs, or any other editor.<br><br><h3>
Staging changes</h3>
To indicate that every new and modified file in your working directory should be "staged" for inclusion in the next commit, run git add without any arguments. You can also specify files or filetypes. For example, the following command would stage all the new and modified files under the bionic directory and its subdirectories:<br><br>$ git add bionic/*<br><br>Run git help add to see more ways to use git add.<br><br><b>When is git add optional?<br></b>
<br>If you add new files, you must stage them using git add before you run git commit. However, if you are only modifying or deleting files, you can skip git add if you use the -a option with git commit. For more details, see the "Committing changes" section further down.<br><br><h3>
Using repo status <br></h3>
-To see the status of the current branch, run <br><br>$ repo status .<br><br>For information about how to interpret the results of repo status, see <a href="{@docRoot}source/git-repo.html#TOC-status">Using Repo and Git</a>
-.<br><br><h3>
+To see the status of the current branch, run <br><br>$ repo status .<br><br>For information about how to interpret the results of repo status, see <a href="{@docRoot}source/git-repo.html#TOC-status">Using Repo and Git</a>.<br><br><h3>
Using git diff</h3>
To see uncommitted changes, cd into the project directory and run <br><br>$ git
diff <br><br>Without any arguments, git diff will show you the differences
@@ -113,8 +108,7 @@
. For more information, see <a href="{@docRoot}source/git-repo.html#TOC-download">Using Repo and Git</a>
.<br><br><h2>
Using the Gerrit code-review tool <br></h2>
-You can open Gerrit by visiting whatever URL is returned to you from the repo upload command, or by visiting <a href="https://review.source.android.com/">https://review.source.android.com</a>
-/.<br><br><h3>
+You can open Gerrit by visiting whatever URL is returned to you from the repo upload command, or by visiting <a href="https://review.source.android.com/">https://review.source.android.com</a>.<br><br><h3>
Viewing the status of uploaded changes <br></h3>
To check the status of a change that you uploaded, open <a href="https://review.source.android.com/mine">Gerrit</a>
, sign in, and click MyChanges.<br><b><br></b>
diff --git a/pdk/docs/source/using-eclipse.jd b/pdk/docs/source/using-eclipse.jd
index 1750a20..aa06d16 100644
--- a/pdk/docs/source/using-eclipse.jd
+++ b/pdk/docs/source/using-eclipse.jd
@@ -1,12 +1,13 @@
page.title=Using Eclipse
doc.type=source
@jd:body
-<div><h2><a>About this Document</a>
-</h2>
-<p>This document will help you set up the Eclipse IDE for Android platform development.
-</p>
-
-
+<div>
+<p>This document will help you set up the Eclipse IDE for Android platform development.</p>
+<p><i>Note: if you are looking for information on how to use
+Eclipse to develop applications that run on Android, this is not the right
+page for you. You probably would find <a
+href="http://developer.android.com/sdk/eclipse-adt.html">the Eclipse page on
+developer.android.com</a> more useful.</i></p>
<h2><a>Enter eclipse</a>
</h2>
<h4>