Le 26/05/15 16:00, Shawn McKinney a écrit : > Hello, > > About ten days ago, the repos of this project have undergone scanning by the > SonarQube bug checker: http://en.wikipedia.org/wiki/SonarQube. > > The good news is we have found many potential problems with all blocking and > critical violations fixed. There is still work to be done and I’ll keep this > list posted. > > In the meantime a JIRA issue has been created to track progress: > https://issues.apache.org/jira/browse/FC-105 > > Below are some links to each repo along with its corresponding sonar pages. > From there you may view the results of the latest code scans, click on links > to view actual offending source code, and check the progress as they get > fixed. There is useful intelligence to be gathered about this project’s code > construction here. > > 1. fortress-core: > > a. git repo: > https://git-wip-us.apache.org/repos/asf/directory-fortress-core.git > > b. sonar scan: > https://analysis.apache.org/dashboard/index?id=org.apache.directory.fortress%3Afortress-core > > 2. fortress-realm: > > a. git repo: > https://git-wip-us.apache.org/repos/asf/directory-fortress-realm.git > > b. sonar scan: > https://analysis.apache.org/dashboard/index?id=org.apache.directory.fortress%3Afortress-realm > > 3. fortress-web: > > a. git repo: > https://git-wip-us.apache.org/repos/asf/directory-fortress-commander.git > > b. sonar scan: > https://analysis.apache.org/dashboard/index?id=org.apache.directory.fortress%3Afortress-web > > 4. fortress-rest: > > a. git repo: > https://git-wip-us.apache.org/repos/asf/directory-fortress-enmasse.git > > b. sonar scan: > https://analysis.apache.org/dashboard/index?id=org.apache.directory.fortress%3Afortress-rest > > Let us know if you have any questions or concerns about this work.
Shawn, that is impressive ! Fortress-core number of issues has drop by more than a factor of 2 (from 2543 down to 1161), with not any blocker and critical issue. Considering that hundreds of the remaining warnings are in HTML files, this is quit a huge imrpovement for Fortress. I'm sure that many warnings are not necessarily important, and some of them are for code that is not yours (Options and CmdLineParser). Congrats ! FTR, I conducted the same kind of cleanup for the API, which is way cleaner now. Not necessarily a funny job, but as Shawn said, this is a good way to catch big errors at the same time, by teh simple fact you review the code in the process. I guess you are ready for a release soon, right ?
