Added the Manifest Update Mojo

[nicstrong]

Added a new mojo for updating various attributes in the manifest. There is some overlap with the VersionUpdateManifest here and will be happy to merge the 2 mojos if you think it is warranted.

Other methods were coincided for accomplishing the same results but were eventially discarded:

1. aapt has various command line switches (e.g. --version-code and --version-name). This method was ruled out as it will only insert the attributes, not replace an existing attribute. This meant we could have some sensible defaults checked into source code control allowing the build to work outside environments without maven support.
2. Using resource filtering. This has 2 problems. In eclipse it does not seem to be able to package the filtered manifest file, so complains that the maven property references are invalid in the POM. And using resource filtering it is only possible to do substitution, this is a problem on sharedUserId where it must be omitted if not required.

[mosabua]

I think this should totally be merged with the versions update mojo. Otherwise there is too much overlap and it will be confusing for the user and potentially buggy if both are invoked..

[nicstrong]

Is there any project guidance/standards to merging mojos? For example should I keep the existing mojo name so existing POMs are not broken if we were to rename it? I guess the down side of this would be that the name version-update would be some what ambiguous as it would do a lot more after the merge. Maybe I should ask on the mailing list.

[mosabua]

This will go out in the 3.0.0 alpha release. Do whatever makes the most sense from an API/configuration point of view. It should be clean and easy to understand. Asking on the mailing list is def a good idea.

[mosabua]

At this stage we are on hold waiting for Nic's magic ;-)

[nicstrong]

Hi,

Finally got around to merging these 2 mojo's. Changes in the request are :

1. I have rebased my manifestupdate-mojo branch on top of the latest master.
2. I have merged the existing VersionUpdateMojo into the new ManifestUpdateMojo dropping the old versionNameUpdate flag as this is now covered by the more flexable versionName flag (which defaults to ${project.version} to emulate the older versionNameUpdate flag).
3. Renamed all the existing tests from version-tests to manifest-tests and added new tests for all the extra code I added.

[mosabua]

Awesome work!! Thanks.