This repository has been archived by the owner on Oct 26, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 113
migration_guide
Jan Berkel edited this page Nov 15, 2011
·
2 revisions
Upgrading the plugin was not a 1:1 match unfortunately. While most of the logic is the same, some the build objects had to be renamed significantly. Names that made sense for project definition mixin's are now objects.
For those of you who are familiar with the android plugin's previous definition, here's a quick match to the important things:
-
AndroidProject
==AndroidProject.androidSettings
-
BaseAndroidProject
==AndroidBase.settings
-
AndroidLibraryProject
==AndroidBase.settings
-
DdmSupport
==AndroidDdm.settings
-
Startable
==AndroidLaunch.settings
-
Installable
==AndroidInstall.settings
-
TypedResources
==TypedResources.settings
-
MarketPublish
==AndroidMarketPublish.settings
-
AndroidManifestGenerator
==AndroidManifestGenerator.settings
-
AndroidTest.androidSettings
==AndroidTestProject
-
AndroidTest.settings
==AndroidLibraryTestProject
All settings and tasks are placed in the Android
config, so be sure to
override the settings in the appropriate scope. For example, to override the
useProguard
setting you must do it the following way:
import AndroidKeys._
useProguard in Android := false
Every setting and task used in the plugin can be found in AndroidKeys
, akin to
sbt.Keys._
- Getting started
- Scala versions
- Android Manifest generation
- Typed resources references
- ProGuard
- DDMS integration
- Building Java Android projects
- Building NDK projects
- Consuming Android Library projects
- Github integration
- Building Android Test Projects
- Password Manager
- Releasing to the Android Market
- Projects using sbt-android-plugin
- Contributors