Dan Sănduleac
Dan Sănduleac
This was working on 1.28.x, I encountered this as soon as VsCode updated to 1.29.0.
I know there have been some previous discussions on this topic, so wanted to address the counter arguments: * the set of built-ins should be small * we can create...
You can do `dependsOn 'dockerTagLatest'` ;)
Here's where they introduced this feature: https://docs.gradle.org/4.6/release-notes.html#convenient-declaration-of-annotation-processor-dependencies They go into it a bit more in the blog post linked there, but the gist is that only annotations (e.g. `Value.Immutable`) need...
It looks like `dependencySubstitution` takes an `Action`, not a Closure, and `module` is a method on that `DependencySubstitutions`. Not sure how or when groovy decides to implicitly look up things...
Hey @jerryshao, thanks for using GCV! Internally we've had this situation come up as well once or twice, but we usually advise to make a new repo when encountering this...
dependencyManagement section in the generated POM.xml contains entries from unrelated configuration?
Sorry I didn't see this. GCV will configure _every_ java project in your build, unless you tell it to skip a project. This includes 1) enforcing locks on that project...
dependencyManagement section in the generated POM.xml contains entries from unrelated configuration?
@dweiss that's surprising, if what you said is indeed the case (that this dependency is "only declared (transitively) in a configuration that is used internally within the build file"). From...
This is because we attempted to stop exposing `versions.props` constraints in the published POM (#193). In order to achieve that, we had to stop injecting constraints into _all_ configurations that...
Interesting! We've actually seen this internally as well, but didn't investigate yet since we don't use kotlin very widely. For some context on the GCV side, we do some sketchy...