gradle-lint-plugin
                                
                                 gradle-lint-plugin copied to clipboard
                                
                                    gradle-lint-plugin copied to clipboard
                            
                            
                            
                        lintExcludes causes crash
What might be the cause that adding one private jar to my compile classpath crashes autoLintGradle task with the "Could not resolve all dependencies for configuration ':lintExcludes'" error. Also I can see this error: Error from [com.netflix.nebula.lint.rule.GradleLintRule$1] processing source file [null].
Using Gradle version 3.5.1 and latest gradle lint plugin. 4.0.1 seem to have some other issues with some plugins, thats why I haven't started to use that yet.
Stacktrace give interensting error that does not exacly help me forward: Caused by: java.lang.IllegalStateException: Unexpected parent dependency id 401. Seen ids: [512, 513, 2, 258, 514, 515, 516, 261, 517, 518, 263, 519, 520, 521, 522, 523, 524, 525, 526, 272, 529, 274, 530, 531, 532, 533, 534, 535, 536, 537, 282, 538, 539, 540, 285, 541, 542, 543, 288, 544, 545, 290, 548, 549, 550, 297, 325, 327, 329, 331, 332, 334, 336, 81, 338, 83, 340, 85, 342, 343, 345 , 347, 349, 95, 351, 353, 98, 355, 101, 105, 361, 107, 363, 109, 365, 367, 112, 369, 114, 371, 118, 120, 122, 124, 126, 383, 128, 385, 387, 133, 135, 137, 139, 141, 398, 143, 408, 411, 422, 428, 430, 436, 438, 441, 446, 447, 448, 449, 450, 195, 451, 452, 198, 199, 455, 456, 201, 203, 463, 464, 209, 211, 469, 214, 470, 215, 471, 472, 217, 219, 475, 476, 477, 224, 228, 230, 486, 487, 233, 239, 498, 499, 244, 500, 501, 502, 247, 503, 249, 506, 507, 508, 509, 510, 511]
Decided to ask about it here before I start to trace and debug it myself, maybe someone has had similar issues.
We saw an issue like this when projects had circular dependencies.
I'm project foo, I depend on bar, bar depends on foo. Had to exclude foo from bar.
That's where I'd start looking
Just faced the same exception, but I had no circular dependency: in my case I fixed by moving project dependencies to the top of the list.