Re: Problem with site plugin and custom language mojos

Does anyone haven any ideas on how to fix this? My guess is that the custom life-cycle that the site bits are forking is somehow not picking up the extra dependencies which need to be configured on the maven-plugin-plugin... and which are configured for normal builds, but freak out when generatin

Re: Problem with site plugin and custom language mojos

ntext: http://www.nabble.com/Problem-with-site-plugin-and-custom-language-mojos-tf3749900s177.html#a10655507 Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For addit

Re: Problem with site plugin and custom language mojos

I think I wrote too soon. The patch I referred to fixes a problem I've had with *Java* plugin site generation, and in the stack trace Jason gives below, the line number in PluginXdocGenerator.java looks earlier in the file than the area to which the patch at the linked-to issue applies. Sorry for

Re: Problem with site plugin and custom language mojos

See for a patch that fixes this. - Steve Jason Dillon wrote: > As many of you know I've been working on Groovy integration for Maven > 2... and I've recently (er well a few weeks ago) gotten things hooked up > to allow mojos to be implemented in Groovy. >

Problem with site plugin and custom language mojos

As many of you know I've been working on Groovy integration for Maven 2... and I've recently (er well a few weeks ago) gotten things hooked up to allow mojos to be implemented in Groovy. I've started to use this to build other plugins, but I've just run into a rather annoying problem with t