You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Benson Margulies <bi...@gmail.com> on 2012/10/23 22:12:56 UTC

Site plugin running, apparently, for ever

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
definitely running executions bound to validate. If wanted something
to run very early in the normal lifecycle and not when building the
site, any suggestions?

I see a lot of messages about forking, and it seems to be running the
same stuff over, and over, and over again.

mvn site:site does not suffer from this effect.

Any suggestions for tracking this down?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Site plugin running, apparently, for ever

Posted by Barrie Treloar <ba...@gmail.com>.
On Wed, Oct 24, 2012 at 10:59 AM, Benson Margulies
<bi...@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 file.
Manually go through this and cull everything that is not telling you
which plugin is running and why.

You will be left with the call tree of the plugins.

I'm assuming at this point it will be obvious what plugin is not
behaving the way you expect it to.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Site plugin running, apparently, for ever

Posted by Benson Margulies <bi...@gmail.com>.
On Tue, Oct 23, 2012 at 7:45 PM, Barrie Treloar <ba...@gmail.com> wrote:
> On Wed, Oct 24, 2012 at 9:28 AM, Benson Margulies <bi...@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 bunch of the usual, and then ...
>>
>> [INFO] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>> [INFO] Forking Juggernaut Release Distribution 0.9.101-SNAPSHOT
>> [INFO] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>
>> The gmaven execution is bound to 'validate', which isn't even supposed
>> to be in the site lifecycle as previously noted.
>>
>> Or, some of the Forking follows just after
>> maven-javadoc-plugin:2.8.1:aggregate (aggregate) @ jug-setup-bt-root
>
> See
>
> http://maven.apache.org/plugins/maven-javadoc-plugin/aggregate-mojo.html
>
> "Invokes the execution of the lifecycle phase generate-sources prior
> to executing itself."
>
> So that's why verify is being run.
>
> I had this problem with enforcer bound to validate and being run
> because of source:jar forking.

OK, that explains the forks, but not iterating infinitely in a loop
forking the top of the build (and all the interior pieces).

>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Site plugin running, apparently, for ever

Posted by Barrie Treloar <ba...@gmail.com>.
On Wed, Oct 24, 2012 at 9:28 AM, Benson Margulies <bi...@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 bunch of the usual, and then ...
>
> [INFO] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> [INFO] Forking Juggernaut Release Distribution 0.9.101-SNAPSHOT
> [INFO] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
> The gmaven execution is bound to 'validate', which isn't even supposed
> to be in the site lifecycle as previously noted.
>
> Or, some of the Forking follows just after
> maven-javadoc-plugin:2.8.1:aggregate (aggregate) @ jug-setup-bt-root

See

http://maven.apache.org/plugins/maven-javadoc-plugin/aggregate-mojo.html

"Invokes the execution of the lifecycle phase generate-sources prior
to executing itself."

So that's why verify is being run.

I had this problem with enforcer bound to validate and being run
because of source:jar forking.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Site plugin running, apparently, for ever

Posted by Benson Margulies <bi...@gmail.com>.
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 Distribution 0.9.101-SNAPSHOT
[INFO] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

The gmaven execution is bound to 'validate', which isn't even supposed
to be in the site lifecycle as previously noted.

Or, some of the Forking follows just after
maven-javadoc-plugin:2.8.1:aggregate (aggregate) @ jug-setup-bt-root
>>>.




On Tue, Oct 23, 2012 at 6:12 PM, Barrie Treloar <ba...@gmail.com> wrote:
> On Wed, Oct 24, 2012 at 6:42 AM, Benson Margulies <bi...@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: 'validate' is not
>> listed as part of the site lifecycle, yet mvn site-deploy is most
>> definitely running executions bound to validate. If wanted something
>> to run very early in the normal lifecycle and not when building the
>> site, any suggestions?
>>
>> I see a lot of messages about forking, and it seems to be running the
>> same stuff over, and over, and over again.
>
> I had a problem with lots of unnecessary forking.
>
> Running with -X spews out lots of information, but forcing myself to
> sift through it found that I was using maven-source-jar:jar (which
> forks) when I switched to :jar-no-fork problem went away.
>
> You might have something similar.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Site plugin running, apparently, for ever

Posted by Barrie Treloar <ba...@gmail.com>.
On Wed, Oct 24, 2012 at 6:42 AM, Benson Margulies <bi...@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: 'validate' is not
> listed as part of the site lifecycle, yet mvn site-deploy is most
> definitely running executions bound to validate. If wanted something
> to run very early in the normal lifecycle and not when building the
> site, any suggestions?
>
> I see a lot of messages about forking, and it seems to be running the
> same stuff over, and over, and over again.

I had a problem with lots of unnecessary forking.

Running with -X spews out lots of information, but forcing myself to
sift through it found that I was using maven-source-jar:jar (which
forks) when I switched to :jar-no-fork problem went away.

You might have something similar.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


RE: Site plugin running, apparently, for ever

Posted by Martin Gainty <mg...@hotmail.com>.
i would roll back from the maven-site-plugin 3.0 betas to an older more stable version such as 2.2
<build>
  <plugins>
    <plugin>
     <groupId>org.apache.maven.plugins</groupId>
     <artifactId>maven-site-plugin</artifactId>
     <version>2.2</version>
     <executions>
       <execution>
        <id/>        
         <phase>validate</phase>
         <goals>
             <goal>jar</goal>
         </goals>
       </execution>
     </excecutions>
   </plugin
  </plugins>
</build>

do you see the same behavior when binding specifically validate phase to a stable version?

forking:
perhaps the LifecycleExecutor calculateForkedExecutions(MojoExecution, MavenSession) is inserting too many entries into the queue
can you force
mojoExecution.getForkedExecutions().isEmpty() to be true
 in 
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: bimargulies@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
> 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
> definitely running executions bound to validate. If wanted something
> to run very early in the normal lifecycle and not when building the
> site, any suggestions?
> 
> I see a lot of messages about forking, and it seems to be running the
> same stuff over, and over, and over again.
> 
> mvn site:site does not suffer from this effect.
> 
> Any suggestions for tracking this down?
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>