I have:
a depends on b
b depends on a

Both a & b are subprojects of the same parent. However, I don't have any
pregoals or prereqs. I am running "maven dashboard" or maven "site", and
I get the cycle errors.

I am able to produce jars for both, which I would think would cause more
of a cycle problem. There is dashboard data in both the a & b projects.
Why doesn't the dashboard plugin just read from that? What is it doing
that causes the cycle?

Brian

> That error message sounds like a werkz error (the goal processor)
> 
> This occurs when you have a dependency loop (via pre goals / prereqs)
> 
> a depends on b
> b depends on c
> c depends on a
> 
> Probably worth checking to see if you are pregoaling one way in the 
> master project and then another way in the sub project - anything 
> dashboard related might also be worth looking at more closely.
> 
> 
> 
> 
> Brian Burridge wrote:
> 
> >I mispoke. Its happening on two subprojects, that are both one level below the 
> >parent.
> >
> >I can create jars (which means compiling is ok) and generate the site for all the 
> >projects, but I can't run the Dashboard report. When I do I get the error.
> >
> >Brian
> >
> >  
> >
> >>Brian Burridge <[EMAIL PROTECTED]> - Mon, Dec 15, 2003:
> >>
> >>    
> >>
> >>>I have a subproject that is dependent on the parent project, and the
> >>>parent project is dependent on the sub project. This doesn't cause a
> >>>problem normally, because there are jars of both, and they both just use
> >>>each others jars. However, when running the following goal from the main
> >>>project I get the error below. Any suggestions?
> >>>      
> >>>
> >> Please note I might be wrong, but it seems you're not supposed to
> >> construct such dependencies with multiproject. I've read some other
> >> multiproject project.xmls and they were structured like:
> >> main project
> >>     multiproject
> >>     sub project 1
> >>         extends main
> >>         depends of sub project 2
> >>     sub project 2
> >>         extends main
> >>         depends of sub project 1
> >>
> >> instead of your structure:
> >> main project
> >>     multiproject
> >>     depends on sub project
> >>     sub project
> >>         extends main
> >>         depends on main
> >>
> >> I don't if there's a way to handle your structure.
> >>
> >>-- 
> >>Lo�c Minier <[EMAIL PROTECTED]>
> >>    
> >>
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >  
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to