Skip to content
This repository

Jun 19, 2012

  1. Indrajit Raychaudhuri

    Move to SBT 0.12.0-RC2

    authored June 18, 2012

Mar 23, 2012

  1. Indrajit Raychaudhuri

    bump up `ReservedCodeCacheSize` for 64bit jvm

    authored March 23, 2012

Mar 22, 2012

  1. Indrajit Raychaudhuri

    use `-XX:+UseCompressedOops` for 64 bit jvm

    authored March 18, 2012
  2. Indrajit Raychaudhuri

    Move to SBT 0.12.0-M2

    authored March 16, 2012

Mar 08, 2012

  1. Indrajit Raychaudhuri

    Remove -XX:+UseCompressedOops since it works for 64bit JVM only

    authored March 09, 2012

Mar 04, 2012

  1. Indrajit Raychaudhuri

    - Update to SBT 0.12.0-M1

    - Push down system property java.util.logging.config.file to more localized scope
    - Tweak liftsh properties to be more reliable and have lower footprint
    authored March 01, 2012
  2. Indrajit Raychaudhuri

    Move to SBT 0.11.2

    authored February 22, 2012

Nov 08, 2011

  1. Tim Nelson

    Issues 1117,1148,1149 - Add update method in MongoRecord, Add java.ut…

    …il.logging.config system property to default build options, MongoRecord should reset dirty flags on save
    authored November 08, 2011

Aug 21, 2011

  1. Indrajit Raychaudhuri

    Make jar path more unambiguous

    authored August 21, 2011

May 15, 2011

  1. Indrajit Raychaudhuri

    Update SBT to 0.7.7

    authored May 16, 2011

Apr 05, 2011

  1. Indrajit Raychaudhuri

    upgrade SBT to 0.7.5

    authored April 05, 2011

Mar 23, 2011

  1. Indrajit Raychaudhuri

    upgrade SBT to 0.7.5.RC1

    authored March 23, 2011

Feb 12, 2011

  1. Indrajit Raychaudhuri

    Split liftsh options, modifying LIFTSH_OPTS is safer now. You can now…

    … do:
    
    LIFTSH_OPTS="-Dpublish.remote=true -Xmx3g" ./liftsh clean-plugins reload update publish
    authored February 12, 2011

Feb 05, 2011

  1. Indrajit Raychaudhuri

    - Update SBT for new project layout

    - Using SBT 0.75.RC0 now
    - Add SBT launcher with liftsh wrapper for convenience
    authored February 06, 2011
Something went wrong with that request. Please try again.