Besides static analysis tools, what do you think about starting to use a code review tool? I've noticed https://reviews.apache.org/ but there was no tuscany group. Is there something else available inside the ASF? Have you used something else in the past? For me at least it would be really useful to get feedback from the more experienced Tuscany devs. Submitting patches through a code review tool also seems more appropriate. And why not, checking each others code before commit can only bring benefits (as far as i know, Rietveld [1] assigns a reviewer based on the person that made the latest changes on most of the files, that seems useful). Thoughts?
[1] http://code.google.com/p/rietveld/ It can be installed on AppEngine if we want a tuscany dedicated instance. On Wed, Jan 26, 2011 at 12:39 PM, dsh <daniel.hais...@googlemail.com> wrote: > Didn't know that you were not aware of the fact that there are Eclipse > plug-ins available for FindBugs, PMD etc. :) > > At IBM I am additionally using Rational Software Analyzer which can be > used inside in Eclipse and it as well integrates into the CI system of > Rational Team Concert. > > Cheers > Daniel > > On Wed, Jan 26, 2011 at 11:34 AM, Mike Edwards > <mike.edwards.inglen...@gmail.com> wrote: > > On 26/01/2011 10:23, Mike Edwards wrote: > >> > >> On 24/01/2011 18:13, César Couto wrote: > >>> > >>> Dear developers, > >>> > >>> I am a PhD student at UFMG, Brazil and as part of my research I am > >>> making a study about the relevance of the warnings reported by the > >>> FindBugs bug finding tool. > >>> > >>> Since I am planning to use Tuscany as a subject system in my research, > >>> I would like to know if Tuscany's developers usually run FindBugs as > >>> > >>> part of the system development process. > >>> > >>> Thanks in advance, > >>> > >>> Cesar Couto > >>> > >>> -- > >>> http://www.decom.cefetmg.br/cesar > >> > >> Cesar, > >> > >> Thinking about this further, I would like to point out that many of us > use > >> Eclipse when building and > >> testing the code for Tuscany. > >> > >> Many of the basic static analysis items are dealt with by the code > assist > >> feature of Eclipse - and > >> many of us rely on that without even thinking about it. > >> > >> Perhaps rather than having a separate tool like FindBugs it would be > more > >> interesting to investigate > >> the possibility of extending the checking that Eclipse performs - > Eclipse > >> already does check some of > >> the things that FindBugs checks, but not all of them. It would be far > >> preferable to us Eclipse users > >> to have static check done as we edit...then you absorb things without > even > >> thinking about them, > >> which is often the most effective way. > >> > >> > >> Yours, Mike. > > > > I'll answer my own question here. > > > > There ARE additional code plugins for Eclipse, for example as discussed > > here: > > > > > http://codedependents.com/2009/07/01/top-5-static-analysis-plugins-for-eclipse/ > > > > > > It might be good to ask why Eclipse don't include some of these > > out-of-the-box rather than requiring delelopers to go download & install > > extra stuff.... > > > > I note that FindBugs is one of these plugins ;-) > > > > > > > > Yours, Mike. > > >
