PlayN 1.2 archetype has broken android/proguard dependency.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create a new project from playn archetype 1.2
2. Note build error:
Plugin execution not covered by lifecycle configuration: 
com.jayway.maven.plugins.android.generation2:android-maven-plugin:3.2.0:proguard
 (execution: default-proguard, phase: process-classes) ...

I updated the plugin to 3.2.0 as a shot in the dark, but to no avail.

I am just disabling the plugin and ignoring android builds for the time being.  
Would I be better off just building from trunk instead?

Original issue reported on code.google.com by a.revolu...@gmail.com on 22 Apr 2012 at 2:31

[GoogleCodeExporter]

This sounds like something that's happening in Eclipse. Is that what you're 
talking about?

Original comment by m...@samskivert.com on 22 Apr 2012 at 3:30

[GoogleCodeExporter]

Aye, it was an eclipse problem.  When I ran mvn android/pom.xml android:deploy, 
it gave me a similar error message, but then complained about targeting android 
platform=11 and gave me a rather helpful command to update my sdk with obsolete 
packages: 
~/workspace/apis/android-sdk-linux/tools/droid update sdk --no-ui --obsolete 
--force

So, It's downloaded a number of gigabytes of binaries I may never use, but a 
subsequent run of android:deploy just succeeded, so it appears as though my 
android sdk is to blame.  I'll restart eclipse and update dependencies when 
it's done it's downloading spree =}

Please note, I was working on playn 1.1.0 without error, and when I updated to 
1.2, I got this error in my existing project, so I tried creating a new project 
from archetype to see if any configuration changed.

If nobody else stars this issue, we could just chalk it up to a 
misconfiguration on my part and move on...

Original comment by a.revolu...@gmail.com on 22 Apr 2012 at 4:10

[GoogleCodeExporter]

I had this issue before, I think I solved it by updating my Android SDK tools 
and my Eclipse ADT plugin to the newest versions, and the eclipse maven 
integration error just disappeared...

Original comment by mbarbe...@gmail.com on 22 Apr 2012 at 8:36

[GoogleCodeExporter]

Ok, I've got it.  I did all the upgrades to every android-related thing I 
possibly could; although that didn't specifically solve my problem, it 
definitely didn't hurt, and may have been required...  I didn't actually have 
the ADT plugin installed on my current workspace, so it's perhaps odd that I 
didn't have any problems earlier...

What did work, however, was upgrading my m2e plugin, and then, in pom.xml, 
where it was complaining about the misconfigured lifecycle target, I right 
clicked, chose "discover new m2e targets", then, importantly, I checked the 
Lifecycles option in the window I was presented with, and the android connector 
was there.

I'm attaching a screenshot of the window from eclipse I used to fix the 
problem, for posterity's sake, in case someone else does a search on the error 
I had.

Please feel free to mark this bug as solved.

Thank you.

Original comment by a.revolu...@gmail.com on 23 Apr 2012 at 3:05

Attachments:

• lifecycle.png

[GoogleCodeExporter]

Oh yeah, I forgot you have to install a m2e connector too... Too bad Eclipse 
did manage Maven in a sooooo crappy way :-\

Original comment by mbarbe...@gmail.com on 23 Apr 2012 at 6:04

[GoogleCodeExporter]

Original comment by samskiv...@gmail.com on 23 Apr 2012 at 3:25

• Changed state: Done