Build Path Error: Cycle Detected

Version: 5.2.9 - build 1020

I cannot get rid of the error messages that appear in the ‘Problem’ tab of Eclipse having the format:

A cycle was detected in the build path of project: moduleName

In the top-level solution and in every one of its subordinate modules, I set the ‘modulesNames’ property to ‘none’, yet the errors persist. There is no additional information in the ‘Problem’ pane and nothing in the log files that tell me what is cyclical. How do I clear these error messages?

Thanks!

Kim

In our case we disconnected every module and then reconnected those that were required.

We discovered (for some reason to do with the upgrade we assume) that there were multiple modules linked to each other where they should not have been - hence the cycle. We only have each module linked to the main solution, we have no module inter dependencies. After doing this the error was gone.

Best of luck with it.

We had the same issue after upgrading to 6. You can also change the Error to only show as a Warning by going to Preferences > Dynamic Languages. Otherwise you have to reorganise your solution so there are not cross dependencies as Kanuna suggested.

Version: 5.2.9 - build 1020

This is happening in version 5, not version 6.

I discovered that there is a .buildpath file (in XML format) for every solution/module in the workspace. Even though I removed all the module links in my solution, the solution .buildpath file is not being updated to reflect those changes (that is, it still has the module links in it). Additionally, the .buildpath files for each of the modules contains a reference to the solution, even though I removed those links within Servoy, so the module .buildpath files are not being updated as well. In Developer, is there a way to force updating the .buildpath files to reflect the changes? In the preferences, under General → Workspace:

Build Automatically
Refresh Automatically

are both checked.

in servoy 5 we don’t do anything with the buildpath, we don’t generate it or alter it.

Thats a 6 thing only, did you use your workspace once with a servoy 6 install?

…did you use your workspace once with a servoy 6 install?

Not on purpose! I did install version 6 several times (inclding the beta releases) but created a separate workspace for it (or, at least, I thought I did). So, how do I back out of this situation? Can I simply delete the .buildpath files in the solution and its modules without corrupting something else? The solution itself appears to be working, it’s just that the errors persist.

yes those build files can be removed in a 5.2 workspace, they are needed in a 6.

Thanks for verifying, Johan…that got rid of the errors!