Bug 507248 - Error message about cycle does not tell where the cycle is
Summary: Error message about cycle does not tell where the cycle is
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.7   Edit
Hardware: All All
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Jay Arthanareeswaran CLA
QA Contact:
URL:
Whiteboard: stalebug bulk move
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-08 15:07 EST by Dani Megert CLA
Modified: 2023-08-09 13:01 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dani Megert CLA 2016-11-08 15:07:05 EST
N20161103-2000.

I got tons of errors that there's a cycle in my build path.

The error message is shown below.

Unfortunately it is useless since it does not show the cycle, but only gives a list of involved projects.



A cycle was detected in the build path of project 'org.eclipse.jdt.compiler.apt'. The cycle consists of projects {org.apache.felix.gogo.command, org.apache.felix.gogo.runtime, org.eclipse.osgi.services, CSVReader, org.eclipse.core.filebuffers, org.eclipse.core.runtime, org.eclipse.equinox.app, org.eclipse.core.resources, org.eclipse.ant.core, org.eclipse.core.variables, org.eclipse.core.expressions, DanisAddOns, org.eclipse.team.core, org.eclipse.compare.core, org.eclipse.team.cvs.core, org.eclipse.jsch.core, org.eclipse.ui, org.eclipse.ui.workbench, org.eclipse.help, org.eclipse.e4.core.services, org.eclipse.e4.ui.workbench.swt, org.eclipse.e4.ui.workbench, org.eclipse.e4.ui.model.workbench, org.eclipse.emf.ecore, org.eclipse.emf.common, org.eclipse.e4.emf.xpath, org.eclipse.e4.ui.services, org.eclipse.e4.ui.di, org.eclipse.e4.core.di.extensions, org.eclipse.e4.core.commands, org.eclipse.emf.ecore.change, org.eclipse.emf.ecore.xmi, org.eclipse.e4.ui.css.core, org.eclipse.e4.ui.css.swt, org.eclipse.e4.ui.bindings, org.eclipse.e4.ui.css.swt.theme, org.eclipse.e4.ui.workbench.addons.swt, org.eclipse.e4.ui.workbench.renderers.swt, org.eclipse.jdt.core, org.eclipse.jdt.compiler.tool, org.eclipse.jdt.compiler.apt, org.eclipse.jdt.ui, org.eclipse.search, org.eclipse.ui.ide, org.eclipse.ui.views, org.eclipse.jface.text, org.eclipse.ui.forms, org.eclipse.ui.workbench.texteditor, org.eclipse.ltk.core.refactoring, org.eclipse.ltk.ui.refactoring, org.eclipse.ui.navigator, org.eclipse.compare, org.eclipse.ui.editors, org.eclipse.team.ui, org.eclipse.debug.core, org.eclipse.debug.ui, org.eclipse.ui.console, org.eclipse.jdt.launching, org.eclipse.jdt.debug, org.eclipse.ui.navigator.resources, org.eclipse.ui.views.properties.tabbed, org.eclipse.jdt.core.manipulation, Eclipse ZRH ALL Tests, org.eclipse.core.expressions.tests, org.eclipse.core.filebuffers.tests, org.eclipse.jdt.text.tests, org.eclipse.text.tests, org.eclipse.jface.text.tests, org.eclipse.jdt.ui.tests, org.eclipse.jdt.junit, org.eclipse.jdt.debug.ui, org.eclipse.jdt.junit.core, org.eclipse.equinox.simpleconfigurator.manipulator, org.eclipse.equinox.frameworkadmin.equinox, org.eclipse.test.performance, org.eclipse.jdt.ui.tests.refactoring, org.eclipse.ltk.core.refactoring.tests, org.eclipse.ltk.ui.refactoring.tests, org.eclipse.search.tests, org.eclipse.ui.editors.tests, org.eclipse.ui.workbench.texteditor.tests, RegexTests, com.oti.zrh.eclipse.tools, org.apache.jasper.glassfish, org.eclipse.ant.launching, org.eclipse.core.externaltools, org.eclipse.ant.tests.core, org.eclipse.ant.tests.ui, org.eclipse.ui.externaltools, org.eclipse.ant.ui, org.eclipse.compare.tests, org.eclipse.core.tests.resources, org.eclipse.core.tests.harness, org.eclipse.pde.junit.runtime, org.eclipse.compare.win32, org.eclipse.core.tests.net, org.eclipse.core.tests.runtime, org.eclipse.debug.examples.core, org.eclipse.debug.examples.memory, org.eclipse.debug.examples.mixedmode, org.eclipse.debug.examples.ui, org.eclipse.debug.tests, org.eclipse.e4.core.tests, org.eclipse.e4.ui.bindings.tests, org.eclipse.e4.ui.dialogs, org.eclipse.e4.ui.tests, org.eclipse.e4.ui.tests.css.core, org.eclipse.e4.ui.tests.css.swt, org.eclipse.egit.core, org.eclipse.egit.ui, org.eclipse.equinox.console, org.eclipse.equinox.ds, org.eclipse.equinox.util, org.eclipse.equinox.event, org.eclipse.equinox.http.jetty, org.eclipse.equinox.http.servlet, org.eclipse.equinox.http.registry, org.eclipse.equinox.jsp.jasper, org.eclipse.equinox.jsp.jasper.registry, org.eclipse.equinox.p2.director.app, org.eclipse.equinox.p2.directorywatcher, org.eclipse.equinox.p2.publisher.eclipse, org.eclipse.equinox.p2.publisher, org.eclipse.equinox.p2.touchpoint.eclipse, org.eclipse.equinox.p2.garbagecollector, org.eclipse.equinox.p2.extensionlocation, org.eclipse.equinox.p2.repository.tools, org.eclipse.equinox.p2.ui, org.eclipse.equinox.security.ui, org.eclipse.equinox.p2.ui.importexport, org.eclipse.equinox.p2.updatesite, org.eclipse.help.base, org.eclipse.help.ui, org.eclipse.help.webapp, org.eclipse.jdt.apt.core, org.eclipse.jdt.apt.pluggable.core, org.eclipse.jdt.apt.ui, org.eclipse.jdt.astview, org.eclipse.jdt.compiler.apt.tests, org.eclipse.jdt.copyrightsaveaction, org.eclipse.jdt.core.tests.builder, org.eclipse.jdt.core.tests.compiler, org.eclipse.jdt.core.tests.model, org.eclipse.jdt.debug.jdi.tests, org.eclipse.jdt.debug.tests, org.eclipse.jdt.jeview, org.eclipse.jdt.ui.examples.javafamily, org.eclipse.jdt.ui.examples.projects, org.eclipse.jface.examples.databinding, org.eclipse.jface.tests.databinding, org.eclipse.jface.tests.databinding.conformance, org.eclipse.jsch.ui, org.eclipse.pde.api.tools, org.eclipse.pde.core, org.eclipse.pde.build, org.eclipse.pde.api.tools.generator, org.eclipse.pde.api.tools.tests, org.eclipse.pde.api.tools.ui, org.eclipse.pde.ui, org.eclipse.ui.intro, org.eclipse.ui.cheatsheets, org.eclipse.ui.views.log, org.eclipse.pde.launching, org.eclipse.ui.trace, org.eclipse.pde.build.tests, org.eclipse.pde.ds.annotations, org.eclipse.pde.ds.core, org.eclipse.pde.ds.tests, org.eclipse.pde.ds.ui, org.eclipse.pde.runtime, org.eclipse.pde.ua.core, org.eclipse.pde.ua.ui, org.eclipse.pde.ui.templates, org.eclipse.pde.ui.tests, org.eclipse.platform, org.eclipse.releng.tests, org.eclipse.releng.tools, org.eclipse.team.cvs.ui, org.eclipse.team.cvs.ssh2, org.eclipse.team.tests.core, org.eclipse.team.tests.cvs.core, org.eclipse.test, org.eclipse.ui.ide.application, org.eclipse.ua.tests, org.eclipse.ui.intro.universal, org.eclipse.ui.intro.quicklinks, org.eclipse.ui.browser, org.eclipse.ua.tests.doc, org.eclipse.ui.editors.bugzilla, org.eclipse.ui.examples.contributions, org.eclipse.ui.examples.fieldassist, org.eclipse.ui.examples.javaeditor, org.eclipse.ui.examples.job, org.eclipse.ui.examples.propertysheet, org.eclipse.ui.examples.rcp.texteditor, org.eclipse.ui.examples.readmetool, org.eclipse.ui.examples.recipeeditor, org.eclipse.ui.examples.views.properties.tabbed.article, org.eclipse.ui.genericeditor, org.eclipse.ui.genericeditor.tests, org.eclipse.ui.monitoring, org.eclipse.ui.net, org.eclipse.ui.tests, org.eclipse.ui.tests.harness, org.eclipse.ui.tests.navigator, org.eclipse.ui.tests.performance, org.eclipse.ui.tests.views.properties.tabbed, org.eclipse.ui.win32, org.mortbay.jetty.server}
Comment 1 Jay Arthanareeswaran CLA 2016-11-08 23:38:20 EST
AFAIK, the dependency is in an order that is listed down, at least in a simple cycle I tried out. But this case seems to be much more complicated.

The problem with the cycle is we don't know where to start and we instead list all the projects that are involved in the cycle.
Comment 2 Dani Megert CLA 2016-11-09 03:40:10 EST
(In reply to Jay Arthanareeswaran from comment #1)
> AFAIK, the dependency is in an order that is listed down, at least in a
> simple cycle I tried out. But this case seems to be much more complicated.
> 
> The problem with the cycle is we don't know where to start and we instead
> list all the projects that are involved in the cycle.

At some point you detect the cycle. That's where we could start to compute the cycle path.

The list is definitely not ordered because the last one 'org.mortbay.jetty.server' does not require the first one 'org.apache.felix.gogo.command'.


After looking closer, some PDE containers looked weird. I then restarted and did a clean + full build and the problem went away.


See also bug 37275.
Comment 3 Dani Megert CLA 2016-12-14 12:22:33 EST
Just ran into the same problem after importing the latest build.
Comment 4 Eclipse Genie CLA 2019-03-24 14:27:57 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 5 Jay Arthanareeswaran CLA 2019-03-26 02:07:56 EDT
(In reply to Dani Megert from comment #2)
> (In reply to Jay Arthanareeswaran from comment #1)
> > AFAIK, the dependency is in an order that is listed down, at least in a
> > simple cycle I tried out. But this case seems to be much more complicated.
> > 
> > The problem with the cycle is we don't know where to start and we instead
> > list all the projects that are involved in the cycle.
> 
> At some point you detect the cycle. That's where we could start to compute
> the cycle path.

In complex cases, that may not be useful if there are too many links in the cycle and by nature, there's no beginning and end in a cycle.

> The list is definitely not ordered because the last one
> 'org.mortbay.jetty.server' does not require the first one
> 'org.apache.felix.gogo.command'.
> 

This is something we can try and fix.
Comment 6 Manoj N Palat CLA 2019-08-27 02:37:15 EDT
Bulk Move Out of 4.13
Comment 7 Eclipse Genie CLA 2021-08-18 11:42:44 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 8 Eclipse Genie CLA 2023-08-09 13:01:48 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.