Permalink
Commits on May 24, 2012
  1. Revert to maven-resource-filtering for updating the version code

    Although some of the Android docutmentino indicates otherwise, the Android
    Market won't let you publish an APK with a lower versionCode than
    previously published for that product. So unfortunately, we can't use
    the nice 'versionCodeUpdateFromVersion' flag from android-maven-plugin v3.
    
    Reverts some of commit 3b80319.
    committed May 24, 2012
  2. add unit test for bitbucket web launch, use https rather than ssh

    I think it's better to default to https rather than ssh clone urls for this
    case because SSH access requires the user to have an SSH key installed -
    even if it's a public repo.
    
    also normalise formatting of AndroidManifest
    committed May 24, 2012
  3. re-enable proguard, mistakenly completely disabled with 1222a40

    Unfortunately it's necessary to manually add various methods used by
    the integration tests - as they're only supplied by the implementation APK,
    and proguard needs to know not to throw them away so they're available when
    the integration tests run.
    committed May 24, 2012
Commits on May 23, 2012
Commits on May 22, 2012
  1. improve status-bar notifications for ICS and also Honeycomb

    Legibility greatly improved, appropriate colours are used to match ordinary
    notifications:
    
    * ICS - the new Notification.Builder and the default notification layout
    are used. The layout is abused slightly, with the 'info' textview being
    updated (tho the id for this textview is hidden) to serve as the progress
    text field.
    
    * Honeycomb and below - differences in colour between different versions
    of Android are handled by using the StatusBarNotificationStyles class,
    which is based off http://stackoverflow.com/a/7320604/438886
    
    The AndroidManifest target sdk update to '13' (ie Honeycomb) is necessary
    to get the nice Holo-styling on the progress bar. Targeting ICS will have
    to wait until ABS support is in:
    
    "Applications targeting [14] or a later release will get these new changes
    in behavior: For devices without a dedicated menu key, the software
    compatibility menu key will not be shown even on phones. By targeting
    Ice Cream Sandwich or later, your UI must always have its own menu UI
    affordance if needed, on both tablets and phones. The ActionBar will take
    care of this for you."
    committed May 22, 2012
  2. compile against Android 4.0...

    committed May 22, 2012
  3. use standard android ids for title & progress views to match ICS

    Notification.Builder uses android.R.id.title & android.R.id.progress in
    it's layouts.
    committed May 22, 2012
Commits on May 21, 2012
  1. upgrade to android-maven-plugin 3.2.0

    This has been a long time coming - the proguard-handling changed with the
    release of 3.0.0, and we've been stuck on an alpha-release ever since...
    finally made it on to the modern version!
    
    The exclusions are unfortunately necessary to avoid Dalvik verifier errors
    as it freaks out over differently proguard-ed versions of the same class.
    committed May 21, 2012
  2. fix up InjectedTestRunner (RG2)

    One new requirement is ensuring that you refer to RoboContext-subclasses...
    committed May 21, 2012
  3. fix some tests by using Application context, rather than activity (RG2)

    A lot of the test-fixes hinge on switching from injecting 'Context'
    (which is taken to mean Activity or Service) to injecting Application -
    which is a context that is always available, and doesn't require your
    classes to be ContextScoped.
    committed May 20, 2012
  4. fix GitAsyncTask test, including correcting base application modules …

    …(RG2)
    
    Note setBaseApplicationInjector() *doesn't* automatically add the
    xml-configured module, if you pass your own modules as parameters.
    committed May 20, 2012
  5. run GitAsyncTask thread within ContextScope (RG2)

    The GAT thread is very likely to have to perform injection, ensuring it's in
    the ContextScope seems wise.
    committed Apr 26, 2012
  6. Update to RoboGuice 2 - various API changes

    Delete special application classes (impl, test) as they're no longer
    necessary.
    
    com.google.inject.internal.Nullable is no longer available.
    committed May 21, 2012
  7. code-formatting apocalypse

    committed May 21, 2012
Commits on May 7, 2012
  1. Push repository-scoping of git operations further down

    This is to simplify stubbing out - so as to not have to worry about
    reposcope at the stubbing level.
    committed May 4, 2012
Commits on May 3, 2012
  1. Provide host IP to android device for integration tests

    Used so the device can hit a local git server running in the maven-running
    host device.
    committed May 3, 2012
Commits on Mar 15, 2012
  1. Delete unused roboservicetestcase

    committed Mar 14, 2012
  2. Robolectric 1.0

    committed Mar 14, 2012
  3. use simplified toy-ssh-agent

    fewer dependencies
    committed Mar 14, 2012
  4. Revert "Use Application rather than Context in CuriousHostKeyRepository"

    This reverts commit 6a90dcc, which seems
    to do the opposite of what it's commit message states...
    committed Mar 15, 2012
Commits on Mar 5, 2012
  1. Default text-entry prompt to password-style behaviour

    This affects both username & password entry, but is the best option for
    a blanket default behaviour
    
    Distinguishing between username and password is a bit more work, and
    there's not much harm making username entry password style as well -
    especially as this is often put into the clone url.
    committed Mar 5, 2012