
The specific reason for this is that it provides @Null and @NotNull annotations which should increase the safety of our code. Many of the bugs which get filed are due to NullPointerExceptions, which could be avoided by tooling using these annotations. The goal is to statically catch this specific class of errors in as many situations as possible, rather than waiting for them to occur at runtime.
26 lines
823 B
Groovy
26 lines
823 B
Groovy
include ':F-Droid:'
|
|
|
|
include ':extern:AndroidPinning'
|
|
include ':extern:UniversalImageLoader:library'
|
|
include ':extern:MemorizingTrustManager'
|
|
include ':extern:libsuperuser:libsuperuser'
|
|
include ':extern:nanohttpd:core'
|
|
include ':extern:jmdns'
|
|
include ':extern:zipsigner'
|
|
include ':extern:spongycastle:core'
|
|
include ':extern:spongycastle:pg'
|
|
include ':extern:spongycastle:pkix'
|
|
include ':extern:spongycastle:prov'
|
|
include ':extern:zxing-core'
|
|
include ':extern:android-support-v4-preferencefragment'
|
|
|
|
include ':support-v4'
|
|
project(':support-v4').projectDir = new File('extern/Support/v4')
|
|
|
|
include ':support-appcompat-v7'
|
|
project(':support-appcompat-v7').projectDir = new File('extern/Support/v7/appcompat')
|
|
|
|
include ':support-annotations'
|
|
project(':support-annotations').projectDir = new File('extern/Support/annotations')
|
|
|