How to resolve cyclic dependency in Maven?

Solution 1:

Maven does not allow cyclic dependencies between projects, because otherwise it is not clear which project to build first. So you need to get rid of this cycle. One solution is the one you already mentioned, to create another project. Another one would be to just move some classes from B to C or vice versa when this helps. Or sometimes it is correct to merge project B and C to one project if there is no need to have two of them.

But without knowing and analyzing why your projects depend on each other it's kinda difficult to suggest the best solution.

So I suggest you can use tools like JDepend or the InteliJ analyse tool to find your problematic classes and based on them find a better design for your software.

Most of the time, I create something like an interface module and and implementation module, which gets rid of most cycles. Check out the answer from Dormouse in this thread and search for Dependency Inversion Principle to get more sources on this topic.

Solution 2:

Creating a new project is indeed one solution.

Dependency Inversion is the second possible solution.

Refer to here for the Acyclic Dependency Principle.

And here for the Dependency Inversion Principle.

Solution 3:

Lets say A project depends on B and B depends on A.

1. Creating new project and move all common classes. This is the first preferred option. If not go with option 2.
2. Try to make one dependency as runtime dependency(Example , A is compile time dependent on B and B is runtime dependent on A). This will help to resolve which jar to build first. In this case, B jar should be build first and then A. Here, runtime means API's can be invoked through reflection.