On Wed, Oct 24, 2012 at 10:59 AM, Benson Margulies
wrote:
> OK, that explains the forks, but not iterating infinitely in a loop
> forking the top of the build (and all the interior pieces).
Can't really help there.
Can only suggest running with -X and writing output to a file.
Manually go throug
On Tue, Oct 23, 2012 at 7:45 PM, Barrie Treloar wrote:
> On Wed, Oct 24, 2012 at 9:28 AM, Benson Margulies
> wrote:
>> Barrie,
>>
>> We have an execution of the gmaven-plugin to set a property -- a
>> property that we don't even need in the site build.
>>
>> I see:
>>
>> [INFO] --- gmaven-plugin
On Wed, Oct 24, 2012 at 9:28 AM, Benson Margulies wrote:
> Barrie,
>
> We have an execution of the gmaven-plugin to set a property -- a
> property that we don't even need in the site build.
>
> I see:
>
> [INFO] --- gmaven-plugin:1.4:execute (default) @ tanuki-unpack ---
>
> and then a bunch of th
Barrie,
We have an execution of the gmaven-plugin to set a property -- a
property that we don't even need in the site build.
I see:
[INFO] --- gmaven-plugin:1.4:execute (default) @ tanuki-unpack ---
and then a bunch of the usual, and then ...
[INFO]
On Wed, Oct 24, 2012 at 6:42 AM, Benson Margulies wrote:
> Using either 3.1 or 3.2, a large project of mine has developed the
> tendency to just keep running the site plugin forever when I run mvn
> site-deploy with 3.0.4.
>
> One aspect of this that I find confusing is this: 'validate' is not
> l
org.apache.maven.plugins.site.DefaultMavenReportExecutor ?
Martin
__
long-winded disclaimer goes here
> Date: Tue, 23 Oct 2012 16:12:56 -0400
> Subject: Site plugin running, apparently, for ever
> From: bimargul...@gmail.com
> To: users@mave
Using either 3.1 or 3.2, a large project of mine has developed the
tendency to just keep running the site plugin forever when I run mvn
site-deploy with 3.0.4.
One aspect of this that I find confusing is this: 'validate' is not
listed as part of the site lifecycle, yet mvn site-deploy is most
defi
