NoClassDefFoundError when project applies java-test-fixtures plugin

[domesticsimian]

I have a gradle based multi-project build with 2 sub-projects. proj2is a simple library applies the java-test-fixtures plugin. proj1 depends on proj2. When I attempt to run any test in proj1 via the Run Test (or Debug Test) Code Lens link, I get a java.lang.NoClassDefFoundError for the library from proj2. Looking at the classpath from the Java Test Runner trace logs, I see that the proj2 path is not included at all (though /proj2/bin/default is, but that's not a real path on my system).

Some things to note:

• In this minimal reproduction of my issue, proj2 doesn't actually have any test fixtures - it simply applies the plugin. In my real-world use case, we do have test fixtures but that's apparently unnecessary.
• Normal language server usage seems to work - vscode knows about the classes, adds the import statement, performs autocompletion, etc.
• Running tests from the command line via ./gradlew build works as expected.

Here is a minimal reproduction of the issue: vscode.zip

[mfussenegger]

Noticed the same problem in CrateDB. We switched from a custom testOutput configuration to test fixtures. (The custom testOutput configuration worked well with Gradle 6.6.x, but didn't work anymore with Gradle 6.7, see eclipse-buildship/buildship#1035).

PR with the change: crate/crate#11290

What may be interesting is that the java.project.getClasspaths command does include the testFixtures classpaths. So merging the results from that command into the classpath from the vscode.java.test.junit.argument commands' result would get the test execution to work.

[PattiShortCake]

Also noticed the same thing when using the following sample project based off Gradle's documentation.

Eclipse and IntelliJ IDEA executes the included tests successfully.

[GSuleimanov]

Got the same issue :( Any plans to fix this?

[rickq]

The same issue. @jdneo could you please comment this?

[jdneo]

Looks like a buildship issue. I tested with buildship@3.16 via the sample project provided by @disturbedsaint and it works well. (Currently the bundled buildship version is 3.15)

[rickq]

@jdneo Many thanks for your prompt response.

Currently the bundled buildship version is 3.15

You probably mean the buildship version 3.1.5, right?
https://github.com/eclipse/buildship/tags

Then it would mean that we have to wait until the buildship 3.1.6 is released to get fix for the VSCode?

[jdneo]

@rickq sorry yes I mean 3.1.5.

Then it would mean that we have to wait until the buildship 3.1.6 is released to get fix for the VSCode?

Yes I think so if I understand the problem correctly. Please stay in tune, I'll leave comments here if there's any update.

[jdneo]

update: Buildship just released 3.1.6 snapshot recently. I guess the problem can be resolved in the near future.

[jdneo]

Hi all,

The Language Support for Java(TM) by Red Hat@1.1.0 has been released with the newest buildship. This issue should have been resolved.

Thanks,