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
goes here
Date: Tue, 23 Oct 2012 16:12:56 -0400
Subject: Site plugin running, apparently, for ever
From: bimargul...@gmail.com
To: users@maven.apache.org
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
On Wed, Oct 24, 2012 at 6:42 AM, Benson Margulies bimargul...@gmail.com 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:
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]
[INFO] Forking Juggernaut Release
On Wed, Oct 24, 2012 at 9:28 AM, Benson Margulies bimargul...@gmail.com 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
On Tue, Oct 23, 2012 at 7:45 PM, Barrie Treloar baerr...@gmail.com wrote:
On Wed, Oct 24, 2012 at 9:28 AM, Benson Margulies bimargul...@gmail.com
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:
On Wed, Oct 24, 2012 at 10:59 AM, Benson Margulies
bimargul...@gmail.com 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
