Merge pull request #90 from ClashTheBunny/master

Fix build because of translation.  Update year for copyright.
Fix #88 - Old Robotium not working on Nexus 4

https://github.com/rtyley/agit/issues/88
Update to latest version of scala-maven-plugin - requires Maven 3.0.4
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] BUILD SUCCESS
[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...

https://github.com/rtyley/agit/issues/78
https://github.com/rtyley/agit/pull/79
[maven-release-plugin] prepare release agit-parent-1.35
[maven-release-plugin] prepare for next development iteration
zipalign skip has always defaulted to 'true'???

Puzzled as to how this ever worked for Agit.

http://maven-android-plugin-m2site.googlecode.com/svn/zipalign-mojo.html
Add the BFG as a sample repo
Update to current version of JGit
Update to AMP 3.5.0

https://groups.google.com/d/topic/maven-android-developers/w5H0oRWJN9I/discussion

Note that non-release builds are now debuggable by default...
[maven-release-plugin] prepare release agit-parent-1.36
[maven-release-plugin] prepare for next development iteration
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.
Update to AMP 3.5.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.
[maven-release-plugin] prepare release agit-parent-1.37
[maven-release-plugin] prepare for next development iteration
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.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=402031
Update to latest version of the scala-maven-plugin
[maven-release-plugin] prepare release agit-parent-1.38