Hi Oleg:
Simple tests show that maven will accept such a project without any
errors or even warnings, but I would like to know whether this kind of
circular "parent"-"aggregator" dependency is bad.
Any opinions why this should not be done?
Not when it comes to the build itself, not. When it comes to site
generation, however, expect "inconsistencies" between the modules menu
and the breadcrumbs. The former will show the parent as a module of the
aggregator while the latter will show a trail like parent > aggregator.
While technically correct (from a Maven point of view), this is probably
something your site's users won't expect. (I have raised an issue about
this: <http://jira.codehaus.org/browse/MSITE-582>.)
Just something to keep in mind.
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]