Cyclic dependency in Maven, chickens and eggs?

If talktome is a general project where other (e. G talktome-tools) depends on, it should not be depend on the more specific projects. Then, it would be wise to get rid of dependency from talktome to talktome-tools Otherwise, you would create a more higher level project (e.

G parent) and put necessary interfaces, classes that can be used by both talktome and talktome-tools to the new project.

If talktome is a general project where other (e. G talktome-tools) depends on, it should not be depend on the more specific projects. Then, it would be wise to get rid of dependency from talktome to talktome-tools.

Otherwise, you would create a more higher level project (e. G parent) and put necessary interfaces, classes that can be used by both talktome and talktome-tools to the new project.

You may move the tests to another maven module like talktome-tests that will do the integration testing. It makes sense especially it seems that talktome shouldn't depend on specific project like talktome-tools. And, test dependencies like talktome-tools should be included with test scope.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.