From ea2c2a00f68a784761e8b68cd91a87693c37a0a7 Mon Sep 17 00:00:00 2001
From: James Moger <james.moger@gitblit.com>
Date: Thu, 18 Apr 2013 08:59:46 -0400
Subject: [PATCH] Documentation

---
 README.markdown |    7 ++++++-
 1 files changed, 6 insertions(+), 1 deletions(-)

diff --git a/README.markdown b/README.markdown
index e1a5fa8..b6587df 100644
--- a/README.markdown
+++ b/README.markdown
@@ -32,4 +32,9 @@
 3. Select your gitblit project root and **Refresh** the project, this should correct all build problems.
 4. Using JUnit, execute the `com.gitblit.tests.GitBlitSuite` test suite.<br/>
 *This will clone some repositories from the web and run through the unit tests.*
-5. Execute the *com.gitblit.Launcher* class to start Gitblit.   
\ No newline at end of file
+5. Execute the *com.gitblit.GitBlitServer* class to start Gitblit GO.
+
+Building Tips & Tricks
+----------------------
+1. If you are running Ant from an ANSI-capable console, consider setting the `MX_COLOR` ennvironment variable before executing Ant.<pre>set MX_COLOR=true</pre>
+2. The build script will honor your Maven proxy settings.  If you need to fine-tune this, please review the [settings.moxie](http://gitblit.github.io/moxie/settings.html) documentation.
\ No newline at end of file

--
Gitblit v1.9.1