Re: [java code coverage] default lifecycle phase of jacoco:prepare-agent

2016-11-14 Thread Evgeny Mandrikov
Hi Andreas, Note that order of goals in same phase is dictated by order of declaration of plugins, so "test" phase is not the best default - most likely will lead to a lot of questions. "prepare-agent" sets property, so "initialize" phase was chosen as a first (prior to "test") best match

Re: [java code coverage] default lifecycle phase of jacoco:prepare-agent

2016-11-12 Thread Mirko Friedenhagen
skipTests and maven.skip.test have different semantics, the first one will only skip execution of surefire and failsafe while with the latter even the compilation of test sources will be skipped. So if you want to run your ITs only you would need skipTests=true and skipITs=false. You could set

Re: [java code coverage] default lifecycle phase of jacoco:prepare-agent

2016-10-29 Thread Mirko Friedenhagen
Hello, you mean skip when maven.test.skip is set? You may achieve this easily by referencing this property in the default-prepare-agent execution. There you may easily redefine the bound phase as well. I use jacoco in projects which have no tests run by surefire or failsafe but the invoker

[java code coverage] default lifecycle phase of jacoco:prepare-agent

2016-10-29 Thread andreas . mandel
Hello list, sorry if this has been already discussed. I just came across this and I'm not sure to understand it fully. I wonder why the jacoco:prepare-agent maven goal is bound to the very early lifecycle phase "initialize"? Wouldn't be a later phase be more reasonable? I assume in most