Maven Android Plugin 2.2.1 released

[Hugo Josefson]

Hi all!

We released Maven Android Plugin 2.2.1 yesterday.

It's mainly a bugfix release. A big thank you to Erik Hjortsberg for
your patches, and also thank you to Manfred Moser for another round of
pom cleanup.

Coincidentally, from this release forward, the plugin requires Apache
Maven 2.2.1. It was needed to fix an issue. You can install the latest
Apache Maven, and find installation instructions here:
http://maven.apache.org/download.html

The Maven Android Plugin now also has the ability to handle resource
overlays when using the "ApkSourcesDependency" feature, introduced in
Maven Android Plugin 2.2.0. You can read more about that here:
http://code.google.com/p/maven-android-plugin/wiki/ApkSourcesDependency

Everything is listed in the changelog too:
http://code.google.com/p/maven-android-plugin/wiki/Changelog

Thanks,
Hugo

[Patrick Renaud]

Hi Hugo.

Hugo, Was the issue with proguard ever solved? Any chance that this release would include a correction to it? Tx. -Patrick

2009/11/17 Hugo Josefson <hu...@josefson.org>

--

You received this message because you are subscribed to the Google Groups "Maven Android Developers" group.
To post to this group, send email to maven-androi...@googlegroups.com.
To unsubscribe from this group, send email to maven-android-deve...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/maven-android-developers?hl=.

[Hugo Josefson]

Hi Patrick, and anyone else wanting to use ProGuard with Maven Android
Plugin!

I started looking into fixing it, and have come as far as getting a
good idea of how to make it happen, resulting in a (possibly
unfinished) patch locally on my machine. It is *not* included in the
2.2.1 release.

The main reason it was not included, is that I haven't had time to
work on it, specifically testing it for any possible regressions. This
fix brings changes to the Maven Lifecycle of the Maven Android Plugin.
That's the *when*, and *in which order* things are compiled and
repackaged etc. Because of that, it needs extra testing, especially
the Eclipse integration which depends on the internals of the plugin's
Maven Lifecycle.

If you want to help, I'd appreciate if you start by filing an issue
for this, in the Issue Tracker. That makes it easier for me to track
and prioritize this in relation to other issues:
http://code.google.com/p/maven-android-plugin/issues/entry

We should then continue our detailed discussions inside that issue.

One thing we will need in any case, for verifying that/if is works, is
a complete example Maven project with all the required ProGuard
configuration and everything specified in the pom.xml and any other
required files, including some source code to compile. It should build
completely when just running 'mvn install', even by me, who isn't used
to configuring ProGuard on my own. If you can, I'd appreciate very
much if you would create such an example project too. It's the
ProGuard configuration stuff I'm almost totally unfamiliar with, so I
need help with that. For the general "complete Maven and Java source
code" project stuff, you could just take one of the Samples projects
and then "proguardify" it:
http://code.google.com/p/maven-android-plugin/wiki/Samples
(I would suggest going with the apidemos-15 project, "proguarifying"
apidemos-15-app. Then we'll try and make sure apidemos-15-
instrumentationtest still runs fine, and then release!)

Thanks,
/Hugo

On Nov 18, 5:27 am, Patrick Renaud <prenau...@gmail.com> wrote:
> Hi Hugo.
>
> Hugo, Was the issue with proguard ever solved? Any chance that this release
> would include a correction to it? Tx. -Patrick
>

> 2009/11/17 Hugo Josefson <h...@josefson.org>

[mosabua]

Thanks a lot for the latest release. In terms of the sample I would
love to see a proguardified sample. I am also wondering if we should
add 1.6 and 2.0 samples in the same fashion we have 1.1 and 1.5.

What are your thoughts?

manfred

[Hugo Josefson]

Yes, we should have all kinds of samples.

They are good both for developers to use as templates, and as
integration tests for the plugin itself as it evolves.

Anyone who has the time, please submit any samples :) Even if you
think it's not perfect for publication, and merely an example of how
to do something, please submit anyway. As a group we can help each
other out with any details...

Thanks,
Hugo