Vscode-java: Any config to disable Circular Dependencies warning/error?

Created on 17 Nov 2018 · 14Comments · Source: redhat-developer/vscode-java

Any config to disable this warning/error? The same project can be loaded in intellij fine without any warning/error.

"A cycle was detected in the build path of project xxx - Build Path Problem"

Environment

Operating System:windows 10
JDK version:1.8
Java extension version: 0.33

Source

hcapp01

Most helpful comment

Can we reopen this? This is a feature of eclipse, so I'm presuming this can be done. Gradle does not allow for cyclic dependencies within configurations. As I understand it, the problem is that you need to be able to support multiple classpaths, one per gradle configuration basically. I know that eclipse cannot support this capability (IntelliJ does), I'm wondering if this extension could.

This is the related issue in buildship:
https://github.com/eclipse/buildship/issues/460

coopstah13 on 7 Aug 2019

👍4

All 14 comments

No it's not possible to disable it. You need to break the cycle.
What kind of project allows such cyclic dependencies? gradle?

fbricon on 29 Nov 2018

Yes, gradle.

hcapp01 on 3 Dec 2018

This is the related issue in buildship:
https://github.com/eclipse/buildship/issues/460

coopstah13 on 7 Aug 2019

👍4

I'm also experiencing this issue. Might make me switch over to IntelliJ after all :/

ragurney on 16 Apr 2020

Why is this closed? Still not able run gradle projects with circular dependencies.

ganezdragon on 11 Sep 2020

We merely take upstream Eclipse projects and integrate them together so they can work in a headless scenario. We definitely rely on other people's work for Core functionalities.
It might be possible in the future for Eclipse Buildship to support some sort of circular project dependencies, when referencing test folders from one project to another, but we can't do anything here in vscode-java until that upstream issue is fixed.

fbricon on 11 Sep 2020

what we're asking for here, is for you to support the option as outlined here: https://github.com/eclipse/buildship/issues/460#issuecomment-297953710

coopstah13 on 11 Sep 2020

@coopstah13 you can try to add

org.eclipse.jdt.core.circularClasspath=warning

to /.settings/org.eclipse.jdt.core.prefs

snjeza on 11 Sep 2020

👍1

@snjeza nope didn't work for me!

ganezdragon on 13 Sep 2020

@ganezdragon Could you provide a project example?

snjeza on 13 Sep 2020

following @snjeza's suggestion, but since I have a multi-project set up with many subdirectories that vscode decided should all get their own .settings folder, I had to update it for every .settings folder in the repo before vscode allowed builds to pass.

shua on 18 Sep 2020

Trawling through https://docs.gradle.org/current/userguide/eclipse_plugin.html , I've found the magic to automate the change above in my build.gradle:

// build.gradle
eclipse.jdt.file.withProperties { props ->
  props.setProperty "org.eclipse.jdt.core.circularClasspath", "warning"
}

may require gradle eclipseJdt to be run

expected result is the following property should be added to any **/.settings/org.eclipse.jdt.core.prefs files that buildship has created, and that should allow builds to proceed instead of erroring on the circularClasspath violations.

org.eclipse.jdt.core.circularClasspath=warning

shua on 22 Sep 2020

@fbricon is it possible to add this as a workspace setting? I work in multi-project gradle build with a few 100 projects, would be tough to maintain setting this per-project.