Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Date: Fri, 26 Aug 2011 16:26:38 +0000 (UTC)
From: "Pierre-Arnaud Marcelot (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Message-ID: 
 <237365674.18090.1314375998852.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (DIRSERVER-1244) Code review + cleaning
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DIRSERVER-1244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pierre-Arnaud Marcelot updated DIRSERVER-1244:
----------------------------------------------

    Fix Version/s:     (was: 2.0.0-M2)
                   2.0.0-M3

> Code review + cleaning
> ----------------------
>
>                 Key: DIRSERVER-1244
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1244
>             Project: Directory ApacheDS
>          Issue Type: Task
>    Affects Versions: 1.5.4
>            Reporter: Emmanuel Lecharny
>            Assignee: Alex Karasulu
>             Fix For: 2.0.0-M3
>
>
> This is a little bit early in the roadmap, but at some point we will need to have a global code review.
> The objectives are :
>  - check for useless classes or code
>  - check that the coding rules are always used all over the code base
>  - eventually question some structural choices (like : are interfaces overused ?)
> A tool can help a lot to do that. I think of Clover, checkstyle, jalopy, or wathever exists that can help.
> We won't change all, but we must be aware of what need to be done to have a better code base. 
> Just remember that nothing is perfect ...

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira