Commits on Nov 24, 2014
Commits on Aug 26, 2014
Commits on Mar 15, 2014
  1. Fix #106 - Clicking 'Refresh' crashes Agit - by upgrade to ABS v4.4.0

    Many thanks to @jwir3 for doing the git-bisect to find out that this was
    introduced by upgrading to ABS 4.3.0 in 78dc1e1.
    The bug in ABS was covered in this issue:
    ...and fixed in this commit:
    committed Mar 15, 2014
Commits on Mar 2, 2014
Commits on Mar 1, 2014
  1. Merge pull request #102 from jwir3/issue-101

    Issue #101: Fix LogFragment so it doesn't incorrectly import resources from handmark.pulltorefresh library.
    committed Mar 1, 2014
  2. Upgrade to AMP v3.8.2

    committed Mar 1, 2014
Commits on Feb 21, 2014
  1. Issue #101: Fix LogFragment so it doesn't incorrectly import resource…

    …s from handmark.pulltorefresh library.
    jwir3 committed Feb 21, 2014
Commits on Dec 22, 2013
  1. Request a large Dalvik heap to help with cloning problematic repos

    Thanks to @pmoor for pointing out the availability of this manifest
    attribute, reporting issue #99!
    Large objects are streamed wherever possible and consequently files of
    this size often won't cause problems, even on a relatively memory
    constrained device like an Android. That works so long as the large
    object is stored as a whole object within the Git packfile. However, if
    the file is similar to any other file stored anywhere within the
    repositories history, they can both be stored in delta format - which
    unfortunately requires a full in-memory representation to decompress.
    committed Dec 22, 2013
  2. Upgrade to latest version of Robotium, to avoid class-cast exception

    Presumbably something great and interesting happened with KitKat...
    committed Dec 22, 2013
  3. Update to JGit v3.2.0

    committed Dec 22, 2013
Commits on Apr 15, 2013
  1. Upgrade to ABS 3.5.3

    This includes the fix for proguard usage on Mac with non-Apple JDK (ie
    Java 7 from Oracle, which is the new default)
    committed Apr 15, 2013
Commits on Mar 11, 2013
  1. Fix #92 properly- don't write malformed refspecs, but tolerate them

    Use JGit library patched to tolerate the malformed refspecs generated by
    JGit v1.0-v2.3.1 for bare-repo clones. From JGit v2.1 onwards (commit
    3da13473), these malformed refspecs were no longer tolerated and would
    stop fetches from updating refs. Normalising the refspecs fixes this
    issue and allows fetches to update refs successfully.
    committed Mar 11, 2013
Commits on Mar 2, 2013
  1. Revert back to JGit 2.0, as JGit 2.1 introduced #92

    Agit v1.36 updated JGit from v2.0 to v2.2. It looks like some change was
    introduced with JGit 2.1 (and all subsequent versions I've checked)
    that makes the ref update fail... perhaps addressing the ref with the
    wrong name (or made it sensitive to using the wrong name), as we see
    debug like this:
    TrackingRefUpdate : refs/heads//master old=AnyObjectId[0000000000000000000000000000000000000000] new=AnyObjectId[ce1e0703402e989bedf03d5df535401340f54b42]
    The ref had a proper value before the ref update, so should not have
    been 00000000... and the correct new value we see is lost, not stored
    to any place I can see. Not sure what's going on with the double slash,
    JGit 2.0 has it too.
    Weirdly, I've only been able to reproduce this issue with repos cloned
    by Agit - so 'testFetchUpdatesFromLocalTestServer()' always passes,
    but 'testFetchUpdatesOnCloneFromLocalTestServer()' fails with JGit 2.1
    and above.
    committed Mar 2, 2013
  2. Update to AMP 3.5.1

    committed Mar 2, 2013
  3. Hack integration-test .zip assets to .zap to evade ProGuard

    The latest version of the Android SDK seems to have changed something
    that means ProGuard now looks into the zip files it finds in the assets
    folder... didn't use to do that.
    committed Mar 2, 2013
Commits on Feb 1, 2013
  1. Update to AMP 3.5.0
    Note that non-release builds are now debuggable by default...
    committed Feb 1, 2013
  2. Add the BFG as a sample repo

    committed Feb 1, 2013
  3. Fix #79 - Specify a version for maven-resources-plugin

    Latest version I see in Maven Central (v2.6) seems to work?
    $ java -version
    java version "1.7.0_09"
    OpenJDK Runtime Environment (IcedTea7 2.3.4) (7u9-2.3.4-0ubuntu1.12.10.1)
    OpenJDK 64-Bit Server VM (build 23.2-b09, mixed mode)
    $ mvn clean install
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 2:04.906s
    [INFO] Finished at: Fri Feb 01 09:00:17 GMT 2013
    [INFO] Final Memory: 55M/690M
    [INFO] ------------------------------------------------------------------------
    Maven 3.0.4, Ubuntu 12.10
    Not sure how this affects issue #78 but the manifest at
    ./agit/target/filtered-manifest/AndroidManifest.xml has the value
    'android:versionCode="130200108"' which is fine...
    committed Feb 1, 2013