Re: Site plugin and forked executions

2012-11-27 Thread Hervé BOUTEMY
Le mardi 27 novembre 2012 21:45:16 Benson Margulies a écrit : > On Tue, Nov 27, 2012 at 8:48 PM, Hervé BOUTEMY wrote: > > I had a second thought about aggregate reporting plugins (or more > > precisely > > goal). > > > > Since some time, we're applying a new pattern where there is a separate > >

Re: Site plugin and forked executions

2012-11-27 Thread Benson Margulies
On Tue, Nov 27, 2012 at 8:48 PM, Hervé BOUTEMY wrote: > I had a second thought about aggregate reporting plugins (or more precisely > goal). > > Since some time, we're applying a new pattern where there is a separate > reporting goal for aggregate (previously, aggregate was a parameter). > In the

Re: Site plugin and forked executions

2012-11-27 Thread Hervé BOUTEMY
I had a second thought about aggregate reporting plugins (or more precisely goal). Since some time, we're applying a new pattern where there is a separate reporting goal for aggregate (previously, aggregate was a parameter). In the maven parent pom, we're explicitely setting a reportSet configur

Re: Site plugin and forked executions

2012-11-19 Thread Barrie Treloar
Feel like doing the manual cleansing of the output file and just keep * lifecycle events > [DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy] * plugin details > [INFO] >>> maven-javadoc-plugin:2.9:aggregate (report:aggregate) @ accumulo > >>> * forking info messages > [INFO] >

Re: Site plugin and forked executions

2012-11-19 Thread Benson Margulies
The second wasn't involved in this case. The first was. On Mon, Nov 19, 2012 at 2:50 PM, Dennis Lundberg wrote: > Hi > > Yes, most likely. There are a bunch of JIRAs for the Site Plugin about > issues like the one you're experiencing. The two things that stands out > from memory are: > > - aggreg

Re: Site plugin and forked executions

2012-11-19 Thread Dennis Lundberg
Hi Yes, most likely. There are a bunch of JIRAs for the Site Plugin about issues like the one you're experiencing. The two things that stands out from memory are: - aggregate reporting plugins (like Javadoc in your example) - using the "new" way of configuring reporting plugins, i.e. under the Si

Re: Site plugin and forked executions

2012-11-19 Thread Benson Margulies
Or is this the real villan: [DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy] [INFO] [INFO] >>> maven-javadoc-plugin:2.9:aggregate (report:aggregate) @ accumulo >>> [INFO] [INFO] [INFO] Forking accumulo 1.5.0

Re: Site plugin and forked executions

2012-11-19 Thread Benson Margulies
Does the below show the enforcer plugin, of all things, forking? [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-enforcer-plugin:1.0.1:enforce' with basic configurator --> [DEBUG] (s) fail = true [DEBUG] (s) failFast = false [DEBUG] (f) ignoreCache = false [DEBUG] (s) project = Ma

Re: Site plugin and forked executions

2012-11-18 Thread Barrie Treloar
On Mon, Nov 19, 2012 at 11:32 AM, Benson Margulies wrote: > Barrie, I understand this much, but what I don't understand is what to > do about it. Is there any choice other than to stop using reporting > plugins that do the forking? Or can I put the executions of them ahead > of site:site on the co

Re: Site plugin and forked executions

2012-11-18 Thread Benson Margulies
On Sun, Nov 18, 2012 at 7:13 PM, Barrie Treloar wrote: > On Mon, Nov 19, 2012 at 9:39 AM, Brett Porter wrote: >> As Hervé says, it'll depend on the reports you're using. Cobertura forks to >> ensure the tests are run with the instrumented classes - though I believe >> most code coverage plugins

Re: Site plugin and forked executions

2012-11-18 Thread Barrie Treloar
On Mon, Nov 19, 2012 at 9:39 AM, Brett Porter wrote: > As Hervé says, it'll depend on the reports you're using. Cobertura forks to > ensure the tests are run with the instrumented classes - though I believe > most code coverage plugins have some options to inject that into your main > build str

Re: Site plugin and forked executions

2012-11-18 Thread Brett Porter
As Hervé says, it'll depend on the reports you're using. Cobertura forks to ensure the tests are run with the instrumented classes - though I believe most code coverage plugins have some options to inject that into your main build stream and then produce the report on the data at the end. - Bre

Re: Site plugin and forked executions

2012-11-18 Thread Hervé BOUTEMY
cobertura, another usual suspect I really don't understand this aspect, and for the moment, I gave up... Le dimanche 18 novembre 2012 17:50:02 Benson Margulies a écrit : > On Sun, Nov 18, 2012 at 5:45 PM, Hervé BOUTEMY wrote: > > Le dimanche 18 novembre 2012 17:24:14 Benson Margulies a écrit :

Re: Site plugin and forked executions

2012-11-18 Thread Benson Margulies
On Sun, Nov 18, 2012 at 5:45 PM, Hervé BOUTEMY wrote: > Le dimanche 18 novembre 2012 17:24:14 Benson Margulies a écrit : >> Folks, >> >> I myself feel like a bit of a looping site build myself on this >> subject, and I apologize. >> >> The build of Apache Accumulo is showing the 'classic' symptoms

Re: Site plugin and forked executions

2012-11-18 Thread Hervé BOUTEMY
Le dimanche 18 novembre 2012 17:24:14 Benson Margulies a écrit : > Folks, > > I myself feel like a bit of a looping site build myself on this > subject, and I apologize. > > The build of Apache Accumulo is showing the 'classic' symptoms of > running more or less forever with 'site:site', due, app