Updated README to reference new jar

Jonathan Bell [2012-12-02 17:46:28]
Updated README to reference new jar
Filename
README.md
diff --git a/README.md b/README.md
index 3e69e6e..c277885 100644
--- a/README.md
+++ b/README.md
@@ -5,7 +5,7 @@ ChroniclerJ [Chronicler implemented in Java]

 **ChroniclerJ** is a system for recording buggy program executions in the field and reproducing them in the lab. **ChroniclerJ** is our Java implementation of **Chronicler**, a generalized record and replay approach for VM-based languages.

-This repository contains the source and a [runnable binary](https://github.com/Programming-Systems-Lab/chroniclerj/blob/master/chroniclerj-0.4.jar) for **ChroniclerJ**.
+This repository contains the source and a [runnable binary](https://github.com/Programming-Systems-Lab/chroniclerj/blob/master/chroniclerj-0.4.1.jar) for **ChroniclerJ**.

 ###For more information
 Please see our Technical Report:
@@ -16,7 +16,7 @@ Running
 ### Instrumenting your code
 Before deploying your code, you need to run the **ChroniclerJ** instrumenter, which will produce two copies of your program: one for deployment (with logging code), and one for replay purposes (with code that reads back from the log).

-To run the instrumenter, use the command `java -jar chroniclerj-0.4.jar -instrument {-mxLogN} input ouputLocationDeploy outputLocationReplay`, where:
+To run the instrumenter, use the command `java -jar chroniclerj-0.4.1.jar -instrument {-mxLogN} input ouputLocationDeploy outputLocationReplay`, where:
 * `{-mxLogN}` is an optional parameter indiciating that at most `N` items should be stored in the in-memory logfile before it is flushed to disk
 * `input` is the path that contains the .class files, .jar files, etc that need to be instrumented (e.g. what you would be deploying normally)
 * `outputLocationDeploy` is where you would like the generated code (for deployment) to be placed
@@ -30,7 +30,7 @@ Deploy your code as you normally would, but deploy the code that was instrumente
 When an uncaught exception ocurrs, **ChroniclerJ** generates a test case. You can manually invoke this process (e.g. from your own exception handler) by calling the method `ChroniclerJExceptionRunner.genTestCase()`. Users are notified that a test case was generated, which is placed in the current working directory and has the name format chroniclerj-crash-*currenttime*.test. The test case file contains all logs necessary to replay the execution.

 ### Replaying test cases
-To replay the failed executions, run the command `java -jar chroniclerj-0.4.jar -replay testCase {classpath}`, where
+To replay the failed executions, run the command `java -jar chroniclerj-0.4.1.jar -replay testCase {classpath}`, where
 * `testCase` is the test case to run
 * `{classpath}` is a space-delimited classpath passed to your program when it starts to replay

@@ -77,4 +77,4 @@ This project makes use of the following libraries:
 * [Log4j](http://logging.apache.org/log4j/), (c) 1999-2012, Apache Software Foundation, released under the Apache License 2.0
 * [XStream](http://xstream.codehaus.org/, (c) 2003-2006, Joe Walnes and (c) 2006-2009, 2011 XStream Committers, released under [a BSD license](http://xstream.codehaus.org/license.html)

-The authors of this software are [Jonathan Bell](http://jonbell.net), [Nikhil Sarda](https://github.com/diffoperator/) and [Gail Kaiser](http://www.cs.columbia.edu/~kaiser/). The authors are members of the [Programming Systems Laboratory](http://www.psl.cs.columbia.edu/), funded in part by NSF CCF-1161079, NSF CNS-0905246 and NIH 2 U54 CA121852-06.
\ No newline at end of file
+The authors of this software are [Jonathan Bell](http://jonbell.net), [Nikhil Sarda](https://github.com/diffoperator/) and [Gail Kaiser](http://www.cs.columbia.edu/~kaiser/). The authors are members of the [Programming Systems Laboratory](http://www.psl.cs.columbia.edu/), funded in part by NSF CCF-1161079, NSF CNS-0905246 and NIH 2 U54 CA121852-06.