Remove Java PC support.

talk/app/webrtc/java/README

Index: talk/app/webrtc/java/README
diff --git a/talk/app/webrtc/java/README b/talk/app/webrtc/java/README
index 454046cb12268646a1e6a42816e644ffa4fe7277..e3e8593c118edd6c14476b25af112f1b2afeb3e7 100644
--- a/talk/app/webrtc/java/README
+++ b/talk/app/webrtc/java/README
@@ -2,22 +2,10 @@ This directory holds a Java implementation of the webrtc::PeerConnection API, as
 well as the JNI glue C++ code that lets the Java implementation reuse the C++
 implementation of the same API.
 
-To build the Java API and related tests, build with 
-OS=linux or OS=android and include
-build_with_libjingle=1 build_with_chromium=0
+To build the Java API and related tests, build with OS=android
 in $GYP_DEFINES.

[phoglund, 2016/02/02 08:04:43]

Nit: pull up to previous line (?)

[perkj_webrtc, 2016/02/03 17:00:03]

Done.

 
 To use the Java API, start by looking at the public interface of
 org.webrtc.PeerConnection{,Factory} and the org.webrtc.PeerConnectionTest.
 
-To understand the implementation of the API, see the native code in jni/.
-
-An example command-line to build & run the unittest:
-cd path/to/trunk
-GYP_DEFINES="build_with_libjingle=1 build_with_chromium=0 java_home=path/to/JDK" gclient runhooks && \
-    ninja -C out/Debug libjingle_peerconnection_java_unittest && \
-    ./out/Debug/libjingle_peerconnection_java_unittest
-(where path/to/JDK should contain include/jni.h)
-
-During development it can be helpful to run the JVM with the -Xcheck:jni flag.
-
+To understand the implementation of the API, see the native code in jni/.