search

pitate7777777 / maven-android-plugin

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

Wrong handling for scope: compile - provided #454

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. create two apklib modules
2. one apklib module depends from the other
3. one apklib uses resources and objects from the other apklib
4. compile with scope compile or provided to see the effect

What is the expected output?
The apklib is compiled without compiler errors

What do you see instead?
The apklib unpacked files or the code of this apklib cannot compiled: Cannot 
find R file (always) or other objects from depended apklib (scope provided only)

What version of maven-android-plugin are you using?
3.8.0 / 3.8.3

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

The generated R file is not in class path or wrong generated. On MAC there are 
no problems, but on Windows :( 
The problem of scope handling is that in scope 'provided' no files from 
depended apklib is unpack (ergo not in classpath), ergo there is an compiler 
error if you use objects from the other apklib (only in scope 'provided').

Original issue reported on code.google.com by kl3in3rh...@googlemail.com on 18 Mar 2014 at 5:51

GoogleCodeExporter commented 9 years ago 
It makes no sense to use scope provided for an apklib dependency.

With an apklib the Android resources need to included with the built artifact 
whether that is an apk or another apklib. That implies scope of compile and is 
incompatible with scope provided.

Original comment by william....@xandar.com.au on 18 Mar 2014 at 10:05