Okay, how about just upping the log level to warn for the time being?
At least we can then see where the potential circular deps are before
forcing failed builds upon people.
Mark
On 29/08/2007, Wayne Fay <[EMAIL PROTECTED]> wrote:
> I'm ok with this so long as it would bring along a flag somewhe
I'm ok with this so long as it would bring along a flag somewhere
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 a
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
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
DefaultArtifactColl
