For simplicity and to avoid memory leak when you attach/detach many times, Scalive only supports processes with only the default system class loader

Author: ngocdaothanh

README.rst

@@ -9,31 +9,29 @@ http://stackoverflow.com/questions/4279611/how-to-embed-a-video-into-github-read
 Download
 --------
 
-Extract `scalive-1.0.zip <TODO>`_ you will see:
+Extract `scalive-1.0.zip <TODO>`_, you will see:
 
 ::
 
   scalive/
     scalive
     scalive.bat
-    scalive-client-1.0.jar
-    scalive-agent-1.0.jar
-    scalive-repl-1.0.jar
-    2.10.2/
-      scala-library-2.10.2.jar
-      scala-compiler-2.10.2.jar
-      scala-reflect-2.10.2.jar
-    2.10.3/
-      scala-library-2.10.3.jar
-      scala-compiler-2.10.3.jar
-      scala-reflect-2.10.3.jar
+    scalive-1.0.jar
+
+    scala-library-2.10.2.jar
+    scala-compiler-2.10.2.jar
+    scala-reflect-2.10.2.jar
+
+    scala-library-2.10.3.jar
+    scala-compiler-2.10.3.jar
+    scala-reflect-2.10.3.jar
 
 scala-library, scala-compiler, and scala-reflect of the appropriate version
 will be loaded to your running JVM process, if they have not been loaded.
 
-JARs for Scala 2.10.2 and 2.10.3 are preincluded for convenience. If your Scala
+For convenience, Scala 2.10.2 and 2.10.3 JARs are preincluded. If your Scala
 process is using a different version, you need to manually download the
-corresponding JARS and save them as above.
+corresponding JARs and save them as above.
 
 Usage
 -----
@@ -52,13 +50,6 @@ To connect a Scala REPL console to a process:
 
   scalive <pid>
 
-If there are multiple class loaders in the process, Scalive will list them so
-that you can choose. Then you run again:
-
-::
-
-  scalive <pid> <class-loader-id>
-
 How it works
 ------------
 
@@ -73,27 +64,14 @@ Known issues
 
 1.
 
-Please read:
-http://www.scala-lang.org/old/node/8002
-
-The Scala REPL console needs to know the classpath used by the target process so
-that it can compile the code you type at the console on the fly. Scalive tries
-to get the classpath from the class loader for you.
-
-It's easy when the class loader is of type `URLClassLoader <http://docs.oracle.com/javase/7/docs/api/java/net/URLClassLoader.html>`_
-(just call ``getURLs``). But when the class loader is of other type
-(like `ClasspathFilter <http://www.scala-sbt.org/release/api/index.html#sbt.classpath.ClasspathFilter>`_
-when the process is started by `SBT <http://www.scala-sbt.org/>`_), Scalive must
-solve the problem in the "case by case" style.
-
-Currently, Scalive only supports these process types:
-
-* Process with only one class loader (normal standalone JVM process, like
-  `Play <http://www.playframework.com/>`_ or
-  `Xitrum <http://ngocdaothanh.github.io/xitrum/>`_).
-* Process started by SBT ``run``.
+For simplicity and to avoid memory leak when you attach/detach many times,
+Scalive only supports processes with only the default system class loader,
+without additional class loaders (Ex: normal standalone JVM processes, like
+`Play <http://www.playframework.com/>`_ or
+`Xitrum <http://ngocdaothanh.github.io/xitrum/>`_ in production mode).
 
-If your process/class loader is not supported, please `create an issue <https://github.com/ngocdaothanh/scalive/issues>`_.
+Processes with multiple class loaders like
+`SBT <http://www.scala-sbt.org/>`_ are not supported.
 
 2.