Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Undetected Gradle test dependencies are ignored
See original GitHub issueGiven a Gradle project setup with subprojects:
ab, which depends ona.testartefacts
The b-test.json bloop file generated from bloopInstall does not take the a.testdependency into account (a-test not a dependency and its output dir is not on the classpath). This means bloop test b does not work, instead failing with
❯ bloop test b
Compiling b-test (1 Scala source)
[E] [E4] b/src/test/scala/com/beachape/BSpec.scala:9:3
[E] not found: value it
[E] L9: it("should lol") {
[E] ^
[E] [E3] b/src/test/scala/com/beachape/BSpec.scala:6:12
[E] not found: value yo
[E] L6: assert(yo == "yo")
[E] ^
[E] [E2] b/src/test/scala/com/beachape/BSpec.scala:5:3
[E] not found: value it
[E] L5: it("should yo") {
[E] ^
[E] [E1] b/src/test/scala/com/beachape/BSpec.scala:3:21
[E] not found: type ASpecLike
[E] L3: class BSpec extends ASpecLike {
[E] ^
[E] b/src/test/scala/com/beachape/BSpec.scala: L3 [E1], L5 [E2], L6 [E3], L9 [E4]
Compiled b-test (45ms)
[E] Failed to compile 'b-test'
I’ve put up a basic repro here with more details in the README https://github.com/lloydmeta/bloop-gradle-subprojects
I’ve looked at https://github.com/scalacenter/bloop/issues/800, https://github.com/scalacenter/bloop/issues/808, and https://github.com/scalacenter/bloop/issues/818, which seem to handle this, but it seems to be broken.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Looks like a bug in resolving to the correct sourceset - I’ll look to fix.
For now you should be able to add
testImplementation(project(":a"))as a workaround.FYI - transitive project dependencies will never appear in the
dependenciessection, only theclasspathsectionAnother attempt… I learnt about the
java-libraryplugin that allows users to use theapidependency declaration to export transitive dependencies and thought I’d give that a shot (code at https://github.com/lloydmeta/bloop-gradle-subprojects/tree/two-projects-getByNamed-with-api)I’m not sure if it’s related to the same bug, but it revealed a possible hesienbug/race-condition whereby
b-testsometimes getsa/build/classesin its build path and sometimes getsa-test/build/classes. Not 100% sure why either way:With `a-test/build/classes`
With `a/build/classes`