Add support to ManifestUpdateMojo for customizing the supports-screens element.
added option to filter META-INF/maven/** and META-INF/MANIFEST.MF from
input jars
added possibility to use proguard from a plugin dependency
Two tests are not annotated as tests (but are still executed as part of the test suite). 

Do we need the @Test annotations at all, and if so, shouldn't these two tests have them too?
Add a helper method to either get or create a DOM element in the Manifest XML
Add a test for updating the supports-screens element, and add the missing resizeable attribute.
Add an XmlHelper class to simplify DOM manipulations via the w3c APIs.
Add support for the compatible-screens element.

I had to disable the unit test for now, since the way we make assertions against the Manifest is not deterministic. It tests for order of elements (since it tests against strings), which is unnecessarily strict. The Manifest elements may appear in any order.
Move getOrCreateElement to XmlHelper.
Extract the remaining XML attributes into constants.
Fix the way the configuration is injected in tests; it was accidentally defined outside the manifest block in the POM.
Update documentation.
Output a log message whenever supports-screens or compatible-screens are updated.
Merge branch 'proguard_features' of git://github.com/grundid/maven-android-plugin into proguard-dependency

Conflicts:
	src/main/java/com/jayway/maven/plugins/android/phase04processclasses/ProguardMojo.java

resolved conflict
refactored so that config works like all others (still need to test), also changed from boolean to Boolean so that null value is possible..
Add Emma coverage support for android maven plugin
Capture screenshots from the Android device during integration tests

ddmlib supports capturing screenshots from your Android device, which is
awesome, and this commit adds support for capturing select screenshots
while running your integration tests- ie robotium-style tests that
drive your app -and additionally creates an animated gif of the
resulting sequence, which for example can be pushed to your chatroom on
every build to give a quick visual assessment of the state of the app.

Handling the scheduling of the screenshots is tricky, and to this end
I've created a small framework to address issues around taking
screenshots with ddmlib:

* ddmlib image capture is slow, around 600ms+ per image
* if the device screen is updating, the captured image is likely to show
  a partially-updated framebuffer
* ddmlib is invoked on the development environment side of your setup
  (ie your machine executing the Maven build) - your app code can't
  easily take screenshots itself, but in order to get best screenshot
  results your device screen should not be changing when the screenshot
  is taken

The android-screenshot framework addresses these issues:

https://github.com/rtyley/android-screenshot-lib

Your development environment runs an OnDemandScreenshotService, using
ddmlib to listen for log messages tagged 'screenshot_request'. Your app
integration test code just writes one of these log messages when it wants
a screenshot taken, and the service obliges by capturing an image from
the device. To get the best results, your tests should then pause for a
second so that the screenshot is of a static screen. That simple
operation is wrapped up for convenience in this class (but you don't
have to use it):

https://github.com/rtyley/android-screenshot-lib/blob/master/celebrity/src/main/java/com/github/rtyley/android/screenshot/celebrity/Screenshots.java

For the android-maven-plugin, the screenshots are written to the
'screenshots' folder under the target folder. They are organised into
subfolders based on the friendly device name, so you can get a snapshot
of how your app looks across several different devices very easily
by just running it on a multi-device build - obviously that works with
the emulator too.
Merge pull request #104 from rtyley/screenshots

Capture screenshots from the Android device during integration tests
in progress.. nothing working
Update to bug-fix release of android-screenshot lib

This release fixes parsing of the key-value pairs that can be passed
with log messages to the paparazzo service - these are only used for
naming the screenshot files at the moment.

Additionally, it fixes a race condition that could see the paparazzo
service being shut down at the same time as the last screenshot being
taken, thus corrupting the animated gif. Works much better now :-)
Merge pull request #105 from rtyley/screenshots

Update to bug-fix release of android-screenshot lib