Hi, only for Sonar, as it's the recommended way (cfr. http://docs.codehaus.org/display/SONAR/Analyzing+with+Maven), the tests get executed during the sonar goal, so we avoid executing them twice.
rgrds, juan pablo On Mon, May 27, 2013 at 10:54 PM, Glen Mazza <glen.ma...@gmail.com> wrote: > JP, why are you running "-Dmaven.test.skip=true", the purpose of Jenkins > precisely is to complain when unit test failures occur. > > Glen > > On 05/27/2013 04:29 PM, Juan Pablo Santos Rodríguez wrote: > > cool, thanks! > > br, > juan pablo > > On Mon, May 27, 2013 at 10:26 PM, Jake Farrell <jfarr...@apache.org>wrote: > >> Hi Juan >> I have added the sonar:sonar build step as requested after the clean >> install is run. >> >> -Jake >> >> Juan Pablo Santos Rodríguez <juanpablo.san...@gmail.com> >> May 27, 2013 4:13 PM >> Hi, >> >> apologies on asking more or less for the same thing twice, but we have one >> more Jenkins job to move to Maven. Specifically, >> https://analysis.apache.org/jenkins/job/jspwiki/ performs "ant Sonar >> -Dsonar.*=..." and we would like it to perform a two step build: first >> "mvn >> clean install -Dmaven.test.skip=true" followed by "mvn sonar:sonar" (btw, >> do we have to add any special property or it's enough declaring the maven >> Sonar plugin, nothing to do,..?) >> >> >> thx! :-) >> >> >> > >
