-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major
-
Component/s: cvs-plugin, subversion-plugin
-
Environment:Maven 2.2.1 or Maven 3.0.3
The following error occurs, when "mvn hpi:run" is called in the CVS-plug-in:
hudson.util.CyclicGraphDetector$CycleDetectedException: Cycle detected: Plugin:cvs -> Plugin:subversion -> Plugin:cvs
Pretty much the same happens with the Subversion-plug-in:
hudson.util.CyclicGraphDetector$CycleDetectedException: Cycle detected: Plugin:subversion -> Plugin:subversion
The problem seems to lie in the dependency of these plugins on the jenkins-test-harness
which in turn has a dependency on the Subversion-plug-in.
A workaround is to exclude the Subversion-plug-in in the pom.xml of the CVS-plug-in or the Subversion-plug-in:
<dependency>
<groupId>org.jenkins-ci.main</groupId>
<artifactId>jenkins-test-harness</artifactId>
<version>1.399</version>
<type>stapler-jar</type>
<scope>compile</scope>
<exclusions>
<exclusion>
<artifactId>subversion</artifactId>
<groupId>org.jenkins-ci.plugins</groupId>
</exclusion>
<exclusion>
<artifactId>subversion</artifactId>
<groupId>org.jvnet.hudson.plugins</groupId>
</exclusion>
</exclusions>
</dependency>
Apparently the Subversion-plug-in is not needed in the test harness at the moment, any tests that
are related to Subversion are commented out!
Can the dependency on the Subversion-plug-in be removed permanently from the jenkins-test-harness?
Or is the workaround a possible permanent fix?
Are there any other ways to fix this problem?
