search

aristofanio / maven-android-plugin

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

resourceOverlayDirectory not considered for APKLib projects #384

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Configure both <resourcesDirectory> and <resourceOverlayDirectory> to 
different directories in an APKLib project.
2. Setup the same strings.xml resource on both locations with different string 
values in them (same resource names or different ones doesn't matter).
3. run: mvn clean package to generate apklib

What is the expected output?

The generate apklib should contain a merged/overwritten version of both string 
resources.

What do you see instead?

It keeps the original <resourcesDirectory> version and ignores the overlay 
completely.

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

3.5.1 - 3.5.4-SNAPSHOT

What are the complete output lines of "mvn -version" on your machine?

Apache Maven 3.0.4 (r1232337; 2012-01-17 03:44:56-0500)
Maven home: /usr/share/maven
Java version: 1.6.0_45, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x", version: "10.7.5", arch: "x86_64", family: "mac"

Please provide any additional information below.

Original issue reported on code.google.com by roberto.andrade on 24 May 2013 at 12:53

GoogleCodeExporter commented 9 years ago 
It looks like this was identified and fixed in the past? but I'm still seeing 
issues with it in my project, possibly missing something or this never made 
into the main repo?

https://groups.google.com/forum/#!msg/maven-android-developers/bxmcH4JLAfg/vzvWn
8dJr6QJ

Original comment by roberto.andrade on 24 May 2013 at 12:57

GoogleCodeExporter commented 9 years ago 
Roberto, please provide a project showing the failure.
If not I will close this issue as resolved.

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

GoogleCodeExporter commented 9 years ago 
Will do. Will test on the latest version first to make sure it's still an issue.

Original comment by roberto.andrade on 11 Mar 2014 at 1:36

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:20