When having issues, attach full logs.
use aar(...) which should be implicit anyway, again, attach full logs;
specifically include log of a clean build
By default, android-sdk-plugin forces 1.6 source/target, to change this,
you can do something like:
javacOptions in Compile <<= (javacOptions in Compile) map { _ collect {
case "1.5" => "1.7"
case s => s
}
}
Of course, to use 1.7, you'll need to be on build-tools 19
On Thursday, March 6, 2014 12:13:35 AM UTC-8, David Pérez wrote:
>
> Before reading your recommendations, I've tried Gradle, and it works ok:
> it signs my apk, runs lint, .....
> The problem has been that IDEA doesn't allow me to mix Gradle and
> non-Gradle modules in the same project. A big limitation for me.
>
> So, I've followed your suggestion, and used the android-sdk-plugin.
>
> Problems I'm having:
>
> - If I compile with sbt, I get this error:
>
> AndroidManifest.xml:34: error: Error: No resource found that matches the
>> given name (at 'value' with value '@integer/google_play_services_version')
>>
>
> I think this is due to the fact I'm using play-services
> ("com.google.android.gms" % "play-services" % "4.+") , but its resources
> aren't included.
>
> - If I compile with IDEA 13 (it uses SBT):
>
> java: javacTask: source release 1.7 requires target release 1.7
>>
> even though I have this in build.sbt:
>
> javacOptions ++= Seq("-source", "1.7", "-target", "1.7")
>>
>
> Has this happened to anybody else?
>
> Am Dienstag, 4. März 2014 17:36:29 UTC+1 schrieb Nick Stanchenko:
>>
>> As I mentioned in the other post, the 2nd and the 3rd are the same. The
>> first one is much more actively developed, so it’s probably a better choice
>> for starting out.
>>
>> Nick
>>
>
--
You received this message because you are subscribed to the Google Groups
"scala-on-android" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
