Hi Chandni, Apologies if I was not clear before.
When the checkstyle violation check was added, we have to have allow certain number of violations in mvn. Then we're going through fixing violations. I'm sure it was done in these 2 steps for a reason. But, I was just want make a point that we should try to avoid later work and should take care of it right away. I hope I'm clear now. Thanks, Chinmay. On Fri, Jan 8, 2016 at 12:13 PM, Chandni Singh <[email protected]> wrote: > Chinmay, > > Can you please elaborate what you mean by work loop here? > > Chandni > > On Thu, Jan 7, 2016 at 10:06 PM, Chinmay Kolhatkar < > [email protected]> > wrote: > > > +1 for findbugs. > > We should have static analysis tool integrated as a part of build > process. > > > > Just one suggestion, we should probably fix the existing issues shown by > > static analysis tool and then only include findbugs as a part of build > > process. Otherwise we might end in the work loop similar to checkstyle > > violation fixing. > > > > Thanks, > > Chinmay. > > > > > > On Fri, Jan 8, 2016 at 4:43 AM, Sandesh Hegde <[email protected]> > > wrote: > > > > > +1 > > > > > > On Thu, Jan 7, 2016 at 3:13 PM Pramod Immaneni <[email protected] > > > > > wrote: > > > > > > > I support it. > > > > > > > > On Thu, Jan 7, 2016 at 2:35 PM, Vlad Rozov <[email protected]> > > > > wrote: > > > > > > > > > Hi All, > > > > > > > > > > Quick question - will it be useful to include findbugs into the > apex > > > > maven > > > > > site report or enable it during verify phase? Any other maven > plugins > > > > > (coberture) that will be useful to include into the build or > report? > > > > > > > > > > Thank you, > > > > > > > > > > Vlad > > > > > > > > > > > > > > >
