IntelliJ Idea 12 + Android + Scala nowadays

Solution 1:

Update: You can read the tutorial I wrote about the upcoming new version of SBT-Android (0.7). Most of your concerns should be addressed there. If they are not, then that's a problem.

Update 2: For fairness's sake, there's also a great work in progress : android-sdk-plugin by @pfn on GitHub.

Regarding ProGuard and build times :

• I am, myself, preloading large libraries on my device with sbt-android. This eliminates ProGuard altogether, but requires root.

• android-sdk-plugin's latest version boasts a new ProGuard cache (same as AndroidProguardScala), which is pretty sweet and does eliminate ProGuard in most cases during development.

I've been contributing to SBT-Android for a few months now, so I know it a lot better than the other solutions.

As of now, the plugin is evolving rapidly, with :

• Full IntelliJ support (thanks to SBTIdea) coming very soon (In fact, it already works, I just need to send the pull requests)
• Automatically preload Scala on an emulator, or rooted device (Just run android:preload-{device, emulator}, no Proguard needed for development anymore!)
• Should support simple Gradle projects out-of-the-box with minimal effort (The directory structure is very similar)
• Configuration is a lot easier (Just add the plugin and a project file and you're set!)

The current version doesn't have most of these niceties, but they're coming up in the following weeks. Some documentation is of course going to follow very soon afterwards, with examples and everything I'll think of.

I encourage you to join the Scala on Android Google Group and share your thoughts, by the way. There's also a #sbt-android channel on Freenode if you're into IRC.

Solution 2:

Just wanted to chime in on this. I used https://github.com/yareally/android-scala-intellij-no-sbt-plugin, although I found the instructions to be vague, not having ever used IntelliJ before this.

You've probably got it all sorted out by now and are happy with SBT, but for my purposes I just wanted to test Scala on Android without all the extra bells and whistles. So, here are some little things I had to do to get the no-sbt-plugin stuff working:

I ended up including the scala-compiler.jar (along with the scala-library.jar and scala-reflect.jar) as a Global Library:

That way, the compiler has access to the library & reflection code, otherwise I was getting errors. If you don't include the library, the IDE complains that the compiler needs an associated library, and if you don't include reflect it spits out a bunch of errors at compile time that it cannot find reflect class definitions.

I had to include scala-library.jar as a module dependency as well (which had the side effect of including it under the Libraries section also):

Before doing all that, I had the Scala plugin installed, created an Android project, and simply added a Scala facet (ignore the memory settings, I was fooling around):

Finally, I had to resolve some remaining compilation errors by adding a few "-dontwarn" lines to the proguard txt file. Simple enough.

Works like a charm. Haven't done anything substantial with it yet, but am looking forward to using Scala on my next Android project.