| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Use plain maven-like repository to resolve it,
remove usage of gradle-intellij-plugin
|
|
|
|
|
|
fixes #205
|
|
fixes #224, fixes #197
|
|
Workaround for johnrengelman/shadow#334
|
|
|
|
Fixes #227
|
|
Fix #218
|
|
|
|
This declares the inputs and outputs for the maven-plugin
generatePom task, which improves incremental build support and
as of Gradle 4.3 (updated) automatically creates directory paths
for declared outputs.
Issue: #235
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This reverts commit bca5db0f6176d5299c7e6e7a658d754171210791
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The 2.4.0 build tools delay variant dependency analysis until needed,
thus we do the same; delay processing variant configurations until
Dokka task execution.
Changes also tested on Android Gradle 2.2.0 and 2.3.0.
|
|
|
|
Introduce PackageListService
#KT-16309 fixed
|
|
Such as packageOptions, impliedPlatforms and so on
|
|
|
|
|
|
|
|
GH-146 fixed
|
|
|
|
|
|
Support getting variantManager after android
build tools 2.3.0 API changes
Fix for issue #140
|
|
|
|
#KT-17016 fixed
|
|
|
|
|
|
(they can't be imported anyway)
|
|
specified in command line
|
