You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <di...@incubator.apache.org> on 2005/12/16 16:33:45 UTC
[jira] Created: (DIR-121) Code review + cleaning
Code review + cleaning
----------------------
Key: DIR-121
URL: http://issues.apache.org/jira/browse/DIR-121
Project: Directory
Type: Task
Reporter: Emmanuel Lecharny
Assigned to: Alex Karasulu
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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DIRSERVER-1244) Code review + cleaning
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-1244:
-----------------------------------------
Fix Version/s: (was: 1.5.9)
2.0.0-RC1
Affected to 2.0.0-RC1, we won't release a 1.5.9
> 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-RC1
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-1244) Code review + cleaning
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-1244:
-----------------------------------------
Affects Version/s: 1.5.4
Fix Version/s: 1.5.9
> 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: 1.5.9
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.