Skip to content
This repository has been archived by the owner on Feb 11, 2022. It is now read-only.

Commit

Permalink
Remove mention of signing config support from README
Browse files Browse the repository at this point in the history
  • Loading branch information
mr-archano committed May 29, 2017
1 parent 2bb7e60 commit d8c55b3
Showing 1 changed file with 2 additions and 17 deletions.
19 changes: 2 additions & 17 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,10 +11,9 @@ file that is not checked in as part of your repo for security reasons
your application `BuildConfig` or in some resource file.

This plugin aims to provide a simple way to:
- define handles to a properties file in your build script (à la `signingConfig`)
- define handles to a properties file in your build script
- generate fields in your `BuildConfig` with values from a properties file
- generate resources with values from a properties file
- load signing configurations from a properties file


## Adding to your project
Expand Down Expand Up @@ -195,21 +194,7 @@ In any product flavor configuration (or `defaultConfig`) you can use
}
```

#### 3. Load signing configuration from properties
Instead of inlining your passwords and other details in your build script
you can fill the signing configuration using a properties file.
```gradle
signingConfigs {
release {
signingConfigProperties buildProperties.releaseSigning
}
}
```
The plugin will automatically retrieve all the needed fields from the
properties file. Note: the path of the keystore file is considered relative
to the path of the specified properties file.

#### 4. Typed `buildConfigField` / `resValue`
#### 3. Typed `buildConfigField` / `resValue`
The plugin enhances the `buildConfigField` and `resValue` facilities to
enforce types. To generate a string field in your `BuildConfig` you used to write:
```gradle
Expand Down

0 comments on commit d8c55b3

Please sign in to comment.