Do you know of any way to manually convert an apklib? This is unfortunately a closed-source project which I don't have control over, and it isn't published to a remote Maven repository. I've poked Google but nothing is jumping out at me. I'd certainly have used an aar if I could.
Thanks. On 11/12/2014 2:53 PM, Perry Nguyen wrote: > local apklib is not supported. publish to maven. > > If you cannot publish to maven, re-package as aar, the plugin has support > for local aar. I will not be adding support for local apklib as it is a > dying format. > On Wed Nov 12 2014 at 12:37:43 PM Nolan Darilek <[email protected]> > wrote: > >> Trying to include aspose.words, which is shipped as a jar and .apk. I've >> placed both in libs/, but the apk is not automatically included. >> >> I then tried adding the following to my build.sbt: >> >> apklib("com.aspose" % "aspose-words-android" % "1.12", >> "libs/aspose-words-1.12-libs-android-jdk16.apk") >> >> as a dependency, but SBT claims the dependency isn't found. I'm basing >> this off of these liens from the readme: >> >> ◦ libraryDependencies += apklib("groupId" % "artifactId" % "version", >> "optionalArtifactFilename") >> ◾ Basically, wrap the typical dependency specification with either >> apklib() or aar() to consume the ... >> >> From this I assumed that, if I specified a filename, the apklib wouldn't >> be resolved against a remote repository. What am I missing? >> >> Thanks. >> >> -- >> 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/d/optout. >> -- 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/d/optout.
