I've noticed behavior that changed when upstepping from 0.12.2 to 
0.13.0/0.13.1 which is quite inconvinient:

1. It's not possible to configure the versionCode property anymore in 
afterEvaluate. It get's ignored if you do so. We have some generic android 
script where the versioncode is auto-generated based on a version variable, 
but it has to be done in afterEvaluate in order to configure that variable:
android {
  defaultConfig {
    afterEvaluate {
      versionCode = some_calculated_value //this value is not used in the 
merged manifest
    }
  }
}

2. If the installDebug task fails (which we had as android says it's a 
downgrade because of the issue above), there's no indication printed. I 
believe it really makes sense to print at least something (or even have the 
job fail) if the installation fails. It took me a while to figure out why 
my code did not work while it just did not install.

Tom

-- 
You received this message because you are subscribed to the Google Groups 
"adt-dev" 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