Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Connect a Clojure REPL to running Java or Clojure processes without any special setup
Java Clojure Shell
Branch: master

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.
liverepl-agent
liverepl-server set clojure var jvm.agent/instrumentation to the Instrumentation inst…
.gitignore
LICENSE
README.TXT Added new download urls for binaries
TODO.txt Added TODO
build.xml Added liverepl.sh (thanks to Alex Osborne)
liverepl.bat Added support for REPLs into Tomcat web applications by discovering a…
liverepl.sh clojure jar copied to build dir which makes it likely to find more th…

README.TXT

LiveRepl
========

***
New download locations for binaries:
  http://djpowell.net/files/liverepl-1.0.zip
  http://djpowell.net/files/liverepl-1.1-alpha.zip
***


Start a Clojure REPL connected to any running Java or Clojure process
without needing the process to be setup in any special way beforehand.

Now supports connecting to Tomcat web applications.

You can use the repl to run code, inspect variables, and
redefine Clojure functions.


Clojure Live REPL - 2009-10-18
David Powell <djpowell@djpowell.net>
<http://github.com/djpowell/liverepl>

This software is distributed under the MIT licence.

----------------------------------------

Build
=====

To build:

  Copy clojure.jar to: ./liverepl-server/lib/clojure.jar

  Run ant

The build will be copied to: ./build/

----------------------------------------

Configuration
=============

Edit liverepl.bat to point to your installed JDK

----------------------------------------

Operation
=========

To see a list of running Java processes on the system, and their
process ids, enter:

   liverepl

To see the available ClassLoaders for a specific process, enter:

   liverepl <pid>

      -- where the pid is the process id for the process, obtained in
         the step above.

To connect a repl to the process, enter:

   liverepl <pid> <classloader-id>

      -- where the pid is the process id for the process.
      -- and the classloader-id was obtained in the step above.

   if you aren't sure which ClassLoader to use, try '0', which
   will always be the System ClassLoader.

Something went wrong with that request. Please try again.