Remove unused: var from Clone op and TransportFactory class
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.
code-formatting apocalypse
improve display of unusable network address list supplied for test server
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.
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.
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.
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.
fix up InjectedTestRunner (RG2)

One new requirement is ensuring that you refer to RoboContext-subclasses...
use ActivityInstrumentationTestCase2 constructor available in Froyo
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.
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.
compile against Android 4.0...
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."
improve maven conf for manifest-updating- android-maven-plugin v3
re-enable proguard, mistakenly completely disabled with 1222a40f

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.
Add web launch support for bitbucket.org
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
Merge branch 'web-launch-bitbucket'
[maven-release-plugin] prepare release agit-parent-1.29