Danny Thomas
Danny Thomas
A rule that detects when test dependencies leak on runtime classpaths would be useful.
Aligned versions from fatjars etc are just fine, as long as they're the same class. Would likely allow us to remove the logic in #139, as this would have the...
Doing this manually is error prone and difficult, because of Gradle's decorating of classes to support property and method syntax. For example, you need to do this just to detect...
When I see nebula/gradle lint messages, they sometimes get confused with gradle error messages, and cause confusion. For e.g. This is the message I see this in red: ✖ build.gradle:...
The first attempt at `apply from` support was incompatible with rules that kept state about the call sites in files - each instance of the rule was running against the...
Use of internal classes/service wiring is breaking the rule on recent versions. I've disabled the spec for now to keep our builds passing on the latest versions, so we can...
We need a test that verifies that rules aren't greater than the width allowed, or adjust on the fly.
We list the artifact coordinates, be nice if we indicated this is a project dependency: warning duplicate-dependency-class netflix:projecta:unspecified in configuration 'compile' has 14 classes duplicated by netflix:projectb:unspecified (use --debug for...
We already have a rule to change the version of a declared dependency when the conflict resolved version differs from the declared first orders. We should do the same for...
Have a build script that has dependencies from an `apply from` and `buildscript` dependencies, and the fixes for `unused-dependencies` are appended to the dependencies block within `buildscript`: ``` buildscript {...