That would be my guess as well, but I’ve never tried it. On Tuesday, April 21, 2015 at 3:49:10 PM UTC+1, Jim Fulton wrote: > > On Tue, Apr 21, 2015 at 10:04 AM, Nick Stanchenko <nick....@gmail.com > <javascript:>> wrote: > > In that case you might want to look at the build file: > > https://github.com/macroid/macroid/blob/master/build.sbt. > > The relevant bits are: > > 1) “androidBuildAar” on the first line; > > 2) setting source and target Java levels to 1.7. > > Other than that, each module is a normal android-sdk-plugin project. > > One advantage of AAR publishing is that the supported SDK levels you > specify > > in AndroidManifest.xml (see e.g. > > > https://github.com/macroid/macroid/blob/master/macroid-core/src/main/AndroidManifest.xml) > > > > will be automatically enforced. > > Thanks much. Do you know what issues there might be consuming > aars built using Scala from Java-based android apps? > > I'm guessing that, at a minimum, the consuming app will need > to run proguard and have the Scala libraries as a dependency. > > > Jim > > -- > Jim Fulton > http://www.linkedin.com/in/jimfulton >
-- 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 scala-on-android+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
