anchor.diff:  
   === jMonkeyEngine SDK Android Integration
   
  -Mobile deployment is a “one-click option next to Desktop/WebStart/Applet deployment in the jMonkeyEngine SDK.
  +Mobile deployment is a "`one-click`" option next to Desktop/WebStart/Applet deployment in the jMonkeyEngine SDK.
   
   *  Automatic creation of Android harness and settings.
   **  Ant script build target creates APK file.
  
positive.code: .  Open an existing JME3 project, or create a new JME3 project.
  .  Right-click the project node in the Projects Window and open the Properties.
  .  In the Application&gt;Android Properties, enable Android Deployment, and select an Android target. E.g. `Android 4.2.2` +
  This creates a “mobile folder in your projects directory. This folder contains a complete android project with correct settings to run the application using the AndroidHarness.
  .  (Restart the jMonkeyEngine)
  .  A Mobile Files node appears in the Project window. +
  It lets you edit the MainActivitity.java, the AndroidManifest.xml, and build.properties.
  
  image:jme3/nvyyd.png[nvyyd.png,width="",height=""]
  
  The Android deployment option creates a separate sub-project for android and makes the main project and associated libraries available to the sub-project as libraries. The sub-project can be edited using NBAndroid (see below) or using Eclipse or any other IDE that supports standard android projects. Normally you do not need to edit the android project files. Exceptions are described further below. _The libraries are first added to the android sub-project when the main project is built for the first time._
  
  
negative.code: *  The needed android.jar comes with the plugin and is automatically added to the android build
  *  All non-android project libraries are automatically excluded from the android build. This is currently hard-coded in the build script, check nbproject/mobile-impl.xml for the details.
  *  The main application class parameter for the AndroidHarness is taken from the jme3 project settings when enabling android deployment. Currently it is not updated when you change the main class package or name.
  *  When you disable the mobile deployment option, the whole "`mobile`" folder is deleted.
  *  The "`errors`" shown in the MainActivity are wrongly displayed only in the editor and will disappear when you install NBAndroid (see below).
  *  To sign your application, edit the mobile/build.properties file to point at valid keystore files.
  
  
  