You're oversimplifying it. There is no cycle when you run mvn
install, Maven is misdetecting it.
When you generate a site, if you are to do "install site" on both
without having a working version of either first, then javadoc ->
checkstyle ->javadoc is never going to be a cycle you can fix. You'd
need to install both first, then build the site for both to make it
work.
The reporting dependencies need to only be assessed when you are
generating the site, not building the plugin. Then, it isn't a
problem because you can mvn install without any cycle, and mvn site
has no cycle because the things are already built so the order isn't
important.
What's more, versions need to be honoured. We should be able to use
the last javadoc release (and so no dependency in the reactor) for
the reporting, while building trunk.
Two relatively simple things to fix. The only workaround is to remove
the reporting plugins from the pom altogether (copying it to every
plugin will only work if you leave some of them out, eg no javadoc on
checkstyle).
- Brett
On 29/11/2006, at 4:32 PM, Jason van Zyl wrote:
On 28 Nov 06, at 5:25 PM 28 Nov 06, Brett Porter wrote:
It's filed in JIRA. I think we need to fix Maven.
To allow cycles? I mean the second that cycle was introduced it
made working with the plugins pretty crappy. How about fixing the
cycle?
The only way to fix this is to disable the reporting, or copy it
into every plugin - not really desirable either.
Or fix the cycle??
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
