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: 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 > 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-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org >