#29 Attempt to make Jalopy relocatable to be SCM friendly
Here is an attempt to make Jalopy relocatable in order to be SCM friendly. It is kind of quick and dirty. I haven't invested much time in it, but someone might find it useful.
Basically for History I introduced a ProjectRoot concept as defined in an environment variable. Instead of History's file method using canonical paths, it chops the ProjectRoot (if present) from the paths.
Next I added the ability to relocate the Jalopy settings directory using an environment variable, wrapped the static initalization of Convention in an init call so that we can 're-init' later.
Lastly I added both concepts to the Ant plug-in so that a user can, off each ant task, specify a project root and a settings home so that there isn't any overlap with multiple project workspaces they might have.
Convention.java, History.java and AntPlugin.java replacements off the Jalopy 1.5rc3 codeline
Logged In: YES
user_id=723231
Originator: NO
Looks like a good plan, thanks !