sudeep87 / uimafit

Automatically exported from code.google.com/p/uimafit
0 stars 0 forks source link

run FindBugs on code base (or something similar) #31

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
We should run a library like FindBugs over the uimaFIT code to look for 
potential coding problems.  This came up in the context of issue #30 in which 
we debated about what argument names should look like.  So, minimally, to close 
this issue we should do something to ensure that name shadowing bugs are not 
going to sneak into our code (since we voted down using an argument prefix for 
variable names).  One way to accomplish this is to set the appropriate name 
shadowing compiler warnings/errors settings.  Unfortunately, this causes 
problems for generated code (e.g. jcasgen generated).  

Original issue reported on code.google.com by pvogren@gmail.com on 2 Jul 2010 at 4:40

GoogleCodeExporter commented 8 years ago
To run FindBugs as part of the Maven build use mvn -Pfindbugs. An respective 
profile has been added to the pom.xml of uimafit-parent. You can also use the 
profiles "pmd" for copy-paste detection and "cobertura" for code coverage 
reports. To get all three profiles at once use "-Pfindbugs,pmd,cobertura". Mind 
that adding cobertura will cause all test cases to be executed twice.

Original comment by richard.eckart on 4 Jul 2010 at 12:48

GoogleCodeExporter commented 8 years ago

Original comment by pvogren@gmail.com on 3 Jan 2011 at 10:03

GoogleCodeExporter commented 8 years ago
I am closing this issue. I think there is nothing more to be done here after 
the profiles have been added except to actually run findbugs from time to time, 
which would be the deverlopers task.

Original comment by richard.eckart on 18 Mar 2011 at 4:14