Open arunkumar9t2 opened 3 years ago
Changing missingStrictDeps
calculation to
val missingStrictDeps = result.keys
.asSequence()
.filter { !directDeps.contains(it) }
.map { Paths.get(it) }
.filter { !Files.isDirectory(it) }
.map { JarOwner.readJarOwnerFromManifest(it).label }
.toList()
allows me to compile but I am not sure why JDK directory lands here.
Some (just Maven maybe?) dependencies also end up here with a null label - I had the issue with the coroutines-core-jvm
artifact. Which results in a command suggesting to add null
to the deps of a target.
For now, we're not going to be prioritizing this in advance of 1.5. We should fix it, but it is on an experimental feature, so we may not get it in for 1.5.
Experimental strict deps is still experimental because it falls afoul of a kotlinc bug with abi generation. This bug should increase in priority in advance of making it non-experimental.
Hi, what is the status of bugfix for that? Still actual.
When I try to disable strict deps the build fails with following exception.
In BUILD.bazel
rules_kotlin version:
eae21653baad4b403fee9e8a706c9d4fbd0c27c6
I had a look at
JdepsGenExtension
and it seems we need to check against directory here before passing the keys toreadJarOwnerManifest
?