I'm ok with this so long as it would bring along a flag somewhere <circular.transitive>warn</> vs break or something, with default being break, so we can still accomodate people that are using deps like dom4j and jaxen.
Also, it would need to be well-documented so we can point all the users@ people to the FAQ when they ask the inevitable question several times a week/month without Googling. Even better, I'd like the error message to include a URL to the proper entry in the FAQ, after it has been documented. Wayne On 8/29/07, Brett Porter <[EMAIL PROTECTED]> wrote: > Pretty sure dom4j/jaxen still reference each other :( > > - Brett > > On 30/08/2007, at 12:00 AM, Mark Hobson wrote: > > > Hi there, > > > > I've just encountered the silent disabling of circular dependencies in > > a build whilst refactoring projects. Previously I've seen these > > failing the build, as expected, but it appears that transitive > > circular dependencies are merely logged as debug. See the comment in > > DefaultArtifactCollector line 355 in 2.0.x: "would like to throw this, > > but we have crappy stuff in the repo". > > > > I think we should be at a point where the repo metadata doesn't have > > circular dependencies. I propose to remove this and propagate the > > exception to fail the build - any opinions? > > > > Cheers, > > > > Mark > > > > --------------------------------------------------------------------- > > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
