Add user-level retry to vagrant process
Add support for a local maven mirror/cache, tested against our local artifactory
Nail down the version of Cloudera CDH4 we're using (4.5.0) rather than have us drift forward with new releases
Merge branch 'feature/oozie_sge_retry' into feature/fix_cloudera_dist
Fix URL
Merge branch 'feature/oozie_sge_retry' into feature/fix_cloudera_dist
Revert changes relating to colon. Not sure if this will affect CentOS, but the colon definitely conflicts with vcloud
Revert changes relating to colon. Not sure if this will affect CentOS, but the colon definitely conflicts with vcloud
Revert changes relating to colon. Not sure if this will affect CentOS, but the colon definitely conflicts with vcloud
Update Java 6 to Java 7 and update Tomcat 6 to Tomcat 7
Setup Cloudera Java 7 package
Initial vCloud support

Modified script and template for vCloud support
Set up DNS in minimal script

The vCloud boxes we have don't have DNS configured properly, so this sets up
DNS using Google's servers.
Merge branch 'feature/openstack_vagrant_1_4' into develop

Conflicts:
	vagrant_cluster_launch.pl
Merge remote-tracking branch 'origin/feature/java_7_tomcat_7' into develop

Conflicts:
	vagrant_cluster_launch.pl
Merge remote-tracking branch 'origin/feature/fix_cloudera_dist' into develop
Merge remote-tracking branch 'origin/feature/oozie_sge_retry' into develop

Conflicts:
	vagrant_cluster_launch.pl
Update sample templates to use Seqware 1.0.11
Updated scripts to use tomcat7 instead of tomcat6
Change README to reflect use of Vagrant 1.4.3