Updating post. Adding more content and examples.

_posts/2013-05-25-making-things-simpler.textile

@@ -1,5 +1,5 @@
 ---
-title: Making thing simpler
+title: Making things simpler
 summary: Using the Classpath more, less statics and more testing
 author: James Ladd
 layout: post
@@ -12,5 +12,14 @@ h2. Introduction
 
 Removing the barriers to using Smalltalk is part of what the Redline project is all about and today another step was taken in that direction. The changes that come with this step are big and impact all of the code that has been written to date but the result is a simpler and easier to use Redline. The way you run Redline has changed to use the java classpath to find your Smalltalk files and the codebase has changed to remove a high percentage of static lists and maps which were making it hard to run Redline in a multi-tenancy or multi-language environment. There is also a new suite of Smalltalk tests to exercise each method of the initial Runtime to give you greater confidence Redline works.
 
+h2. Classpath Changes
+
+The Java Virtual Machine knows where to find classes via the Classpath which is a value you can specify on the command line when running Java. Redline now uses this Classpath as well to find your .st files. Like always your .st files can be inside a folder or inside a JAR and Redline will load them. What follows is how to run the Redline Smalltalk Test suite, assuming you have the test suite in the test-classes folder and the required Redline JAR's in the lib folder:
+
+{%highlight sh%}
+java -cp test-classes:lib/redline-0.5-SNAPSHOT.jar:lib/antlr-runtime-3.4.jar:lib/asm-4.1.jar st.redline.Stic st.redline.kernel.TestRunner
+{%endhighlight%}
+
+The above represents a much simpler invocation format and fits the current Java model 100%. In the example above the last two arguments are the Redline Smalltalk invoker (Stic) and the Smalltalk to be invoked (TestRunner).