Closed GoogleCodeExporter closed 9 years ago
GoogleCodeExporter
commented
9 years ago Test against 3.8.3-SNAPSHOT
If the failure stills occurs then provide a project or link to a project that
clearly highlights the failure.
Original comment by william....@xandar.com.au on 17 Feb 2014 at 11:16
GoogleCodeExporter
commented
9 years ago I'm also getting the same issue on my Windows system.
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
19:21:28+0530)
Maven home: c:\maven\v305
Java version: 1.6.0_32, vendor: Sun Microsystems Inc.
Java home: c:\Program Files\Java\jdk1.6.0_32\jre
Default locale: en_IN, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "x86", family: "windows"
Any updates on the fix ?Original comment by vigne...@strumsoft.com on 21 Feb 2014 at 2:54
GoogleCodeExporter
commented
9 years ago @vigneshm
Android-Maven-Plugin requires Maven 3.1.1+
Are you getting this error against the 3.8.3-SNAPSHOT?Original comment by william....@xandar.com.au on 21 Feb 2014 at 10:45
GoogleCodeExporter
commented
9 years ago @William: As mentioned above, I'm using Maven 3.0.5 and Android-Maven-Plugin
v3.7.0Original comment by vigne...@strumsoft.com on 22 Feb 2014 at 5:58
GoogleCodeExporter
commented
9 years ago OK .. well no one is planning on patching this back in version 3.7.0 of the
plugin.
So if you want a fix I suggest you see if it is fixed in 3.8.3-SNAPSHOT
Original comment by william....@xandar.com.au on 22 Feb 2014 at 6:23
GoogleCodeExporter
commented
9 years ago Can you provide a project showing the failure?
That way we at least test whether it still exists?Original comment by william....@xandar.com.au on 10 Mar 2014 at 11:57
GoogleCodeExporter
commented
9 years ago Setup:
Using 3.9.0-SNAPSHOT w/ patch for PR313+PR314, Maven 3.1.1
Modifying the project from #444
Test 1:
apklib depends on
<dependency>
<groupId>com.badlogicgames.gdx</groupId>
<artifactId>gdx-bullet-platform</artifactId>
<version>0.9.9</version>
<classifier>natives-armeabi-v7a</classifier>
</dependency>
<dependency>
<groupId>com.badlogicgames.gdx</groupId>
<artifactId>gdx-bullet-platform</artifactId>
<version>0.9.9</version>
<classifier>natives-armeabi</classifier>
</dependency>
both of those put a libgdx-bullet.so at / inside the jar
If extractDuplicates=false, it will tell you that the two libgdx-bullet.so
files conflict with each other.
If extractDuplicates=true, it compiles fine, but does not include either
libgdx-bullet.so in the resulting apk.
Test 2:
apklib depends on these:
<dependency>
<groupId>com.snappydb</groupId>
<artifactId>snappydb-native</artifactId>
<version>0.2.0</version>
<classifier>armeabi-v7a</classifier>
<type>so</type>
</dependency>
<dependency>
<groupId>com.snappydb</groupId>
<artifactId>snappydb-native</artifactId>
<version>0.2.0</version>
<classifier>armeabi</classifier>
<type>so</type>
</dependency>
APK does not contain the native libs. Perhaps because of:
[DEBUG] Not extracting snappydb-native...
[DEBUG] Not extracting snappydb-native...
Test 3:
Sanity check - moved the Test 2 dependencies directly into the apk project.
That compiled fine and included the native dependencies.
Test 4:
Sanity check - Test 3 + Test 1 w/ <extractDuplicates>true</extractDuplicates>
Same result as #3. Snappy but not badlogic in APK.
So a couple things are obvious from this.
1. we are not currently handling jars that have native dependencies at the root
2. we are not currently handling external native dependencies of APKLIB
3. If it says there are duplicates, they are probably named the same in the
same pathOriginal comment by malac...@gmail.com on 23 Mar 2014 at 5:06
GoogleCodeExporter
commented
9 years ago I have a pull request to handle #2
https://github.com/jayway/maven-android-plugin/pull/319
Still need to figure out the best way of addressing #1Original comment by malac...@gmail.com on 28 Mar 2014 at 7:41
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 PluginOriginal comment by mosa...@gmail.com on 19 May 2014 at 4:20
Original issue reported on code.google.com by
camueller28on 24 Oct 2013 at 6:31Attachments: