kerasking / maven-android-plugin

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

downloaded native libs and apklib #340

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Copy some native libs in to [projectdir]\target\libs\armeabi\
2. Try to build the apklib
3. Check if the apklib contains the native libraries from 
[projectdir]\target\libs\armeabi\

What is the expected output?
native libs are part of the apklib

What do you see instead?
native libs are not part of the apklib.

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

What are the complete output lines of "mvn -version" on your machine?
Apache Maven 3.0.4 (r1232337; 2012-01-17 00:44:56-0800)
Maven home: /pathtomaven/maven/apache-maven-3.0.4
Java version: 1.6.0_26, vendor: Sun Microsystems Inc.
Java home: /usr/lib/jvm/java-6-sun-1.6.0.26/jre
Default locale: en_US, platform encoding: ISO-8859-1
OS name: "linux", version: "2.6.32-37-generic-pae", arch: "i386", family: "unix"

Please provide any additional information below.
Same works for the apk project and native libs are included to apk.

Original issue reported on code.google.com by aguptamo...@gmail.com on 19 Dec 2012 at 10:26

GoogleCodeExporter commented 9 years ago
By default, it will default to
${project.basedir}/libs
not
${project.build.directory}/libs
per 
http://jayway.github.io/maven-android-plugin/apklib-mojo.html#nativeLibrariesDir
ectory

If you would rather put the libs in target, you should specify the 
nativeLibrariesDirectory configuration parameter.

Original comment by malac...@gmail.com on 28 Mar 2014 at 5:24

GoogleCodeExporter commented 9 years ago
We are no longer using the issue tracking system on Google Code. Please refile 
this issue on https://github.com/jayway/maven-android-plugin/issues if you 
still have this problem with the latest release of the Android Maven Plugin

Original comment by mosa...@gmail.com on 19 May 2014 at 4:19