On 27/01/2011 10:11 AM, Phillip Hellewell wrote:
Doesn't anyone know if Maven is supposed to give you an error when
there is a cycle?
If the answer is yes, then I need to figure out what I'm missing.
If the answer is no, then I'll write a plugin to detect cycles and
give an error. I've already got a plugin that detects a version clash
(same artifact in the tree twice with different versions), so I could
just add cycle detection to that one. It will probably be as simple
as checking for myself in the tree of dependencies.
Phillip
On Mon, Jan 24, 2011 at 3:56 PM, Phillip Hellewell<ssh...@gmail.com> wrote:
I don't know if I've lost my mind or what, but Maven is not giving me
an error when I have cyclic dependencies.
I just tried a simple two projects A and B that depend on each other,
and Maven gives me no errors when resolving dependencies.
You can clearly see the cycle when running mvn dependency:tree.
C:\mycomps2\compa>mvn dependency:tree
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building compa
[INFO] task-segment: [dependency:tree]
[INFO] ------------------------------------------------------------------------
[INFO] [dependency:tree {execution: default-cli}]
[INFO] mygroup:compa:pom:1.0.0
[INFO] \- mygroup:compb:zip:vc-all:1.0.0:compile
[INFO] \- mygroup:compa:zip:vc-all:1.0.0:compile
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Mon Jan 24 15:00:16 MST 2011
[INFO] Final Memory: 19M/483M
[INFO] ------------------------------------------------------------------------
Am I losing my mind? What's going on? Does it have something to do
with the fact that I am using the assembly plugin with "zip"
classifer?
Phillip
Does this matter?
Is more than 1 copy of mygroup:compa:zip:vc-all:1.0.0 being included.
It seems silly to make something dependent on itself and I can't imagine how
your would build it in the first place withyout getting an error.
But for mygroup:compa:pom:1.0.0, it will get 1 mygroup:compa:zip:vc-all:1.0.0
and that is what it needs.
I am missing the harm that this does since it will get detected earlier in the
process.
Ron
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
