Buildship interfering with simple run/debug launch

Help/Discuss Buildship
1

I have Java jar/war/ear projects building fine with Gradle via Jenkins. I’m running MyEclipse Enterprise Workbench 2020.5.18. I don’t want Buildship involved in any way. I’m getting this in .log when I launch a simple Java utility class from a utility project:

!ENTRY org.eclipse.core.jobs 4 2 2020-07-22 11:29:49.027
!MESSAGE An internal error occurred during: “Launching …MyClass…”.
!STACK 0
org.eclipse.buildship.core.internal.GradlePluginsRuntimeException: Model not available for …ADependencyProject…
at org.eclipse.buildship.core.internal.workspace.GradleClasspathContainerRuntimeClasspathEntryResolver.resolveRuntimeClasspathEntry(GradleClasspathContainerRuntimeClasspathEntryResolver.java:77)
at org.eclipse.buildship.core.internal.workspace.GradleClasspathContainerRuntimeClasspathEntryResolver.resolveRuntimeClasspathEntry(GradleClasspathContainerRuntimeClasspathEntryResolver.java:66)
at org.eclipse.jdt.internal.launching.RuntimeClasspathEntryResolver.resolveRuntimeClasspathEntry(RuntimeClasspathEntryResolver.java:110)

None of these projects have builders, natures, etc., in their .classpath, .project, and .settings/* files.

Why is Buildship getting called and how do I prevent it?

Cary

2

It shouldn’t happen. The GradleClasspathContainerRuntimeClasspathEntryResolver class is tied to the Eclipse classpath container. Just make sure that your .classpath file doe not contain the following entry:

<classpathentry kind="con" path="org.eclipse.buildship.core.gradleclasspathcontainer"/>
3

Removing that classpathentry cured the problem. Thanks.