You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This Maven Enforcer Rule checks your project for package cycles. It fails the build if any package cycle is found, showing you the packages and classes involved in the cycle.
4
+
5
+
Usage: Add the following plugin to your POM:
4
6
5
7
```
6
8
<plugin>
@@ -19,7 +21,7 @@ Usage: Build and add the following plugin:
@@ -30,6 +32,7 @@ Usage: Build and add the following plugin:
30
32
</plugin>
31
33
```
32
34
33
-
See also: original version at http://stackoverflow.com/questions/3416547/maven-jdepend-fail-build-with-cycles
34
-
35
-
Improved by showing all packages afflicted with cycles and the corresponding classes importing the conflicting packages.
35
+
See also:
36
+
* The original version by Daniel Seidewitz on [Stackoverflow](http://stackoverflow.com/questions/3416547/maven-jdepend-fail-build-with-cycles). Improved by showing all packages afflicted with cycles and the corresponding classes importing the conflicting packages.
37
+
*[JDepend](https://github.com/clarkware/jdepend), the library being used to detect package cycles.
38
+
* For more information about package cycles, see ["The Acyclic Dependencies Principle" by Robert C. Martin (Page 6)](http://www.objectmentor.com/resources/articles/granularity.pdf).
0 commit comments