I agree.  Using Gradle, SBT or Maven as a build system has lots of 
advantages.
I'm using SBT successfully.

Am Samstag, 17. Mai 2014 20:39:22 UTC+2 schrieb Nick Stanchenko:
>
> Yeah, it has been working that way for at least a year. But there are 
> several disadvantages to not using a build system, most notably (from the 
> top of my head):
>
>    - No automatic dependency management.
>    - No command-line builds and tests.
>    - Builds are not easy to reproduce on a different system. Unless you 
>    include the IDEA files in version control. But then you’ll get tons of 
> junk 
>    in commits.
>    - More or less the same as the previous one: being dependent on a 
>    particular IDE.
>    - No ProGuard caching (as in https://github.com/pfn/android-sdk-plugin
>    ).
>
> Perhaps there are others that I didn’t remember and/or list here. The only 
> advantage I see is that one doesn’t have to learn SBT (which can be hard, 
> but is rewarding in terms of productivity). Anyway, I’m convinced that in 
> 2014 a build system is a must :)
> Just my 2¢.
>
> Nick 
>
> On Saturday, May 17, 2014 7:14:31 PM UTC+1, Far Be wrote:
>>
>> I don know is it news for you, but it's possible to develop Android apps 
>> on Scala with Intellij 13 without 3d party plugins, SBT and Proguard.
>>
>> http://stackoverflow.com/questions/23696560/android-scala-intellij-13/23696561#23696561
>>
>

-- 
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.

Reply via email to