Hi Murthy, You might get a better response on a Jenkins mailing list: https://jenkins-ci.org/content/mailing-lists
That said, I do have one question/suggestion: are you using the "Maven-style" job? Or Freestyle job? If you are using the Maven-style job, try switching to Freestyle, and use the "Invoke top-level Maven targets" build step. Then Jenkins behaves faithfully with Maven CLI calls. Conversely, the Maven-style job does some wacky things which can result in different behavior than calling Maven from the command line. Regards, Curtis On Fri, Apr 17, 2015 at 10:48 AM, Gandikota, Murthy < [email protected]> wrote: > Hi All > Using Jenkins 1.596, the jar files are not included in the WAR by maven > which is given the following goals: > clean dependency:tree install -P component clover2:setup test > clover2:aggregate clover2:clover > When I run maven on the command line the WAR is built correctly by > including all the dependent jars. Also, when an upstream project invokes > build, the WAR is built correctly. Can anyone figure out why this is so? > Many thanks for your help > >
