appamatto
appamatto
@yuchangyuan can you explain what the use case for this is?
Thanks! This does seem interesting. Perhaps we could detect when the services directory is present and do the right thing in that case, with a single switch to turn it...
This could be useful, and pretty easy to do with the new code organization.
That's a good idea, I did this with --custom-package which is less useful because it doesn't resolve the .Foo class names.
You may need a resolver that specifies where to find the plugin in project/plugins.sbt: ``` resolvers += Resolver.url("scalasbt releases", new URL("http://scalasbt.artifactoryonline.com/scalasbt/sbt-plugin-releases"))(Resolver.ivyStylePatterns) addSbtPlugin("org.scala-sbt" % "sbt-android-plugin" % "0.6.3-SNAPSHOT") ```
Plugins (I think) don't generally have Scala versions, they are usually indexed by sbt version. Are you talking about building an Android app using Scala 2.10.0?
https://github.com/jberkel/android-plugin/pull/143
I've noticed proguard still getting executed with this override. I'm quite baffled--looking at the code this should never happen, unless I'm misunderstanding the semantics of "lazy".