> Hello,
Hi,
> Seems like a great tool, however I too cannot get the tool to fail
> with cyclical dependencies. Are you sure it works? I'm not.
Yes, I'm sure.
> I have three basic Maven projects, projectA , projectB and projectC.
You don't use maven-architecture-rules-plugin, right? And just old
plain technique which described at
http://architecturerules.googlecode.com/svn/docs/sample-configuration.html?
> In projectA, I have a class A
> In projectB, I have a class B
> And in projectC I have a class C
You sould have a 4th
> So the above projects have cyclical dcependency.
Definetly they have but only from your point of view.
From a-r's point of view all your projects are independent. So:
- projectA contains a single class A w/o any cyclical dependencies
- projectB contains a single class B w/o any cyclical dependencies
- projectC contains a single class C w/o any cyclical dependencies
> Any ideas??
Yes. Move your classes A, B and C into a single project
(i.e. projectA) and you'll see cyclical dependencies from the a-r's
POV ;-)
BTW, maven-architecture-rules-plugin is not ready for a such use
case. It wouldn't detect problems in a multi-module build.
--
MAN-UANIC
Fallon, thanks for providing code samples and the output in your email.
Unfortunately Architecture Rules does not detect indirect cyclic
dependencies yet, only direct dependencies.
> In projectA, I have a class A
> In projectB, I have a class B
> And in projectC I have a class C
A -> B -> C -> A is indirect
A -> B -> A is direct
http://72miles.com/architecturerules/cyclic-dependencies
I hope we can detect indirect dependencies in the future. Perhaps
there is someone out there who is interested in adding this
funcionality.
Fallon, thanks for taking the time to describe this issue to us. I
hope this helps explain the current state of the project in terms of
detecting dependencies.
Good luck.
~ Mike
~ 72miles.com