kerasking / maven-android-plugin

Automatically exported from code.google.com/p/maven-android-plugin
0 stars 0 forks source link

Application fails with NoClassDefFound exception is started using Eclipse's "Run As -> Android Application" #386

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
My application uses Google Play library and if I start the application from 
command line using "mvn android:deploy android:run", if runs fine. But if I try 
to start the application from Eclipse's "Run As -> Android application", the 
application crashes with "java.lang.NoClassDefFoundError: 
com.google.android.gms.R$styleable", when tries to access Google Play library 
classes. m2e-android is installed.

What steps will reproduce the problem?
1. Start the application using Eclipse's "Run As -> Android application"

What is the expected output?
The application should not crash. :)

What do you see instead?
Application crashed with error message "java.lang.NoClassDefFoundError: 
com.google.android.gms.R$styleable"

What version of maven-android-plugin are you using?
3.6.0

What are the complete output lines of "mvn -version" on your machine?
C:\projects\ttl\ttl-app>mvn -version
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 15:51:
28+0200)
Maven home: C:\opt\maven\bin\..
Java version: 1.7.0_21, vendor: Oracle Corporation
Java home: C:\opt\java7\jre
Default locale: en_US, platform encoding: Cp1251
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"

Please provide any additional information below.

Original issue reported on code.google.com by igor.blj...@gmail.com on 24 May 2013 at 8:38

Attachments:

GoogleCodeExporter commented 9 years ago
I have the same issue. I'm using 
https://github.com/mosabua/maven-android-sdk-deployer to install Google stuff 
in my local Maven repo

Original comment by davide.b...@gmail.com on 20 Sep 2013 at 11:45

GoogleCodeExporter commented 9 years ago
This sounds like an issue with Eclipse/m2e not the android-maven-plugin.
If you can build and deploy to your device and it works then AMP has done it's 
job.
If another tool can't run the project insitue then it's a problem with the 
other tool.

Original comment by william....@xandar.com.au on 11 Mar 2014 at 12:38