Maven Android Plugin 2.9.0-beta-1 released

[Hugo Josefson (Jayway)]

Hi developers!

Maven Android Plugin version 2.9.0-beta-1 has been released.

This release includes initial support for Android Library Projects
(apklib), the number one most starred issue in our issue tracker :) I
named this release "beta", because I have not had the opportunity to
do extensive testing with Android Library Projects. Specifically aidl
files in libraries is something that you guys can help test!

Please find details on how to help test this, and links to samples
here:
http://code.google.com/p/maven-android-plugin/wiki/ApkLib

It is important to note that with this functionality, we can help grow
the Android developer community! The artifact named *.apklib which is
built from an Android Library Projects with Maven, are compatible with
non-Maven projects. The .apklib file can easily be used by non-Maven
developers by renaming it to .zip and unpacking it. In the same way,
their Library Projects, zipped up, can be used by Android/Maven
developers like us, by installing it into our ~/.m2/repository with
mvn install:install-file...

Thank you Nick Maiorana for the apklib code, and thank you Eric Bowman
for extra fixes. Also, thank you all for your patience with this!

Thank you Clement Escoffier for adding the configuration option
"extractDuplicates".

The Changelog has more details and links:
http://code.google.com/p/maven-android-plugin/wiki/Changelog

Enjoy!
/Hugo

[ebowman]

Does this happen to include the AIDL support I contributed?

Thanks,
Eric

[Hugo Josefson (Jayway)]

Yes, I was unclear on that. It does.

Please test the AIDL support :)

Thanks,
Hugo

[ebowman]

Hi Hugo,

It's not working for me like it was in my fork.

When I have a dependency topology like this:

+-------+ +-------+ +--------+
| App C | --> | Lib A | --> | Common |
+-------+ +-------+ +--------+
| ^
| |
v |
+-------+ |
| Lib B | --------------------+
+-------+

...I get build failures trying to build App C, due to duplicate class
definitions found.

Basically I am see a class a.b.c.Foo.java in 3 places in App C's
target:

./target/classes/a/b/c/Foo.java
./target/unpack/apklibs/Lib A/src/a/b/c/Foo.java
./target/unpack/apklibs/Lib B/src/a/b/c/Foo.java

I'll (try to) put together a reproduction case and stick it on Github;
not sure I can get to it today.

Thanks,
Eric

On Mar 7, 11:45 am, "Hugo Josefson (Jayway)" <h...@josefson.org>

[Ricardo Gladwell]

Nice work, Hugo. Hoping to have a release for
m2eclipse-android-integration with support for apklib projects soon...

--
Ricardo Gladwell <ricardo....@gmail.com>
http://www.google.com/profiles/ricardo.gladwell
Twitter: @rgladwell - MSN: axo...@gmail.com

> --
> 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=en.
>
>

[Hugo Josefson (Jayway)]

Interesting.

Is "Common" a jar or apklib?

Looking forward to an example. If you want, you can fork the samples
repo and extend it with more classes in "libraryprojects" for your use
case:
https://github.com/jayway/maven-android-plugin-samples/tree/master/libraryprojects

We need that kind of stuff anyways for testing :)

Thanks,
Hugo

[Hugo Josefson (Jayway)]

Cool! That will surely be appreciated by Eclipse users :)

Thanks,
Hugo

On Mar 7, 3:42 pm, Ricardo Gladwell <ricardo.gladw...@gmail.com>
wrote:

> Nice work, Hugo. Hoping to have a release for
> m2eclipse-android-integration with support for apklib projects soon...
>
> --

> Ricardo Gladwell <ricardo.gladw...@gmail.com>http://www.google.com/profiles/ricardo.gladwell

> Twitter: @rgladwell - MSN: axo...@gmail.com
>

[ebowman]

It's an apklib.

I should be able to do this later today.

Great stuff, thanks.

On Mar 7, 10:21 pm, "Hugo Josefson (Jayway)" <h...@josefson.org>
wrote:

> Interesting.
>
> Is "Common" a jar or apklib?
>
> Looking forward to an example. If you want, you can fork the samples
> repo and extend it with more classes in "libraryprojects" for your use

> case:https://github.com/jayway/maven-android-plugin-samples/tree/master/li...

[ebowman]

Here's an example that works with my fork, but doesn't work with 2.9.0-
beta-1

https://github.com/ebowman/maven-android-multimodule-example

Thanks for having a look...

cheers,
Eric

On Mar 7, 10:21 pm, "Hugo Josefson (Jayway)" <h...@josefson.org>
wrote:

> Interesting.
>
> Is "Common" a jar or apklib?
>
> Looking forward to an example. If you want, you can fork the samples
> repo and extend it with more classes in "libraryprojects" for your use

> case:https://github.com/jayway/maven-android-plugin-samples/tree/master/li...

[ebowman]

Curious how this is going? Anything I can do to help? Was the sample
project useful?

Thanks,
Eric

[Manfred Moser]

I think you should move it into a fork of the examples project as a
submodule. Afaik it works with beta2.

manfred

[Hugo Josefson (Jayway)]

Hi Eric,

Thank you for the very clear example! I have unfortunately had little
time for open source projects lately, which is evident from the lack
of release announcement for the 2.9.0-beta-2 release, which I released
a couple of weeks ago. Please see the most up-to-date information on
the Changelog page:

http://code.google.com/p/maven-android-plugin/wiki/Changelog

On the Changelog page, I added a link to my fork of your multimodule
example, in which I made some small changes.

I also agree with Manfred that your example should go into the
official Samples project.

As for the next steps, this is what I see is needed before a 2.9.0
release:
* Posting a release announcement for 2.9.0-beta-2 with credit to
those who added new features and fixed bugs.
* Inventory new Issues posted regarding the apklib functionality:
http://code.google.com/p/maven-android-plugin/issues/list?sort=-id
* Fix those issues and release more betas in the meantime, so
everyone can use the fixes as soon as possible and not have to wait
for the completed 2.9.0.

If you (Eric, or *anyone else reading this*) want to help, please see
what you can do about the issues posted. Some things which everyone
can do with new Issues:
* Determine which things need more details to be able to reproduce
the issue, and ask the poster to for example post their pom.xml.
* If the issue is something that can be answered rather than fixed
with code, please add that as a comment to the issue.
* If the person who posted the issue gave some details about how to
reproduce the error, it is *very helpful* for those who will debug and
create a fix, if you have the opportunity to set up a small sample
project which produces the error. That makes it a lot quicker for
those who debug it to get started! You can put it up as a github
project, or simply attach it as a zip file to the issue.

These things are always very much appreciated!

IIRC, everyone has permission by default to file issues and comment on
them. If you would like to change the status on issues (for example to
be able to mark them as Incomplete when more details are required),
please email me at hu...@josefson.org. This is also appreciated.

Thanks,
Hugo