The JavaDoc for @OptionValues says this and I question the yellow parts:

Besides that the angle brackets are not properly encoded.

The example in userguide shows this:

Copied from briandealwis/cram#5: @student-06 asked

It would be great if we can supply auth creds for registry using parameters since it removes the dependency on credential helpers.

My exact use case is: We are setting up a CI system for UI projects, where we need to push docker images (without daemon) to a local registry which has auth.

异常类型：编译异常

手机型号：

手机系统版本：

Robust版本：0.4.82

Gradle版本：3.2.1

系统：window

个人分析： 看robust的源码是使用gradle2.1.0，配置说明是2.1.0+，include 3.0， 然而个人的是3.2.1； 是不是我本地gradle版本太高 导致不兼容了？

堆栈/日志：(没有添加 --stacktrace，先把当前log附上)
FAILURE: Build failed with an exception.

• What went wrong:
  Execution failed for task ':robust:packageRelease'.

Cannot cast object 'com.android.build.gradle.internal.scop

According to the gradle guide, buildSrc should be preferred over script plugins as it is easier to maintain, refactor and test the code.

Yet none of the samples inside kotlin-dsl have a directory /buildSrc/src/test

So one hand we are on our own to figure out how it works, on the other hand it gives the impression that someone is not walking the walk.

I've only seen AngularJS's Protractor used with JavaScript or TypeScript but it would be awesome to have a Kotlin example.

Please provide:

• Link to build log from https://jitpack.io
  https://jitpack.io/com/github/bumptech/glide/v4.7.1/build.log

• Does the project build on your machine with the same commands (e.g. ./gradlew install) ?
  Haven't tried building locally.

• What error are you seeing?
  Could not resolve all files for configuration ':app:betaReleaseRuntimeClasspath'.

Could not resolve com.gi

So that people aren't confused and use the pre proguard jar. build/libs is a standard place to look, and there is a jar there that looks like the valid build result, however that jar shouldn't be used, so it should ideally be deleted after completion. Could be added to ProguardTask.cleanup or similar.

It runs on ASTs, so it can run in parallel to compilation.

As a potential followup, we can maybe look at making lint optionally run as an implicit concurrent action of building a src target

• I have verified there are no duplicate active or recent bugs, questions, or requests.
• I have verified that I am using the latest version of MaterialStyledDialogs.
• I have given my issue a non-generic title.
• I have read over the README and [Wiki](https://github.com/javiersantos/MaterialStyledDia