You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2008/05/20 05:36:55 UTC

[jira] Commented: (DIRMINA-575) Add the missing Javadoc, add some comments

    [ https://issues.apache.org/jira/browse/DIRMINA-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598168#action_12598168 ] 

Emmanuel Lecharny commented on DIRMINA-575:
-------------------------------------------

For a 2.0, it will be a blocker. If we have to have a 2.0.0-M3, this is not a blocker.

The thing is that we can't say a JIRA issue is a blocker for a future version.

About what has to be added, a complete code review should be done, or at least, using a tool like Enerjy on eclipse of any other tool can tell you where the Javadoc is missing. This is actually what we are doing on Directory : using such a tool to add missing javadoc.

I know this is painfull, but it's a no brainer, and a good thing to do when tired, as it does not need to be very efficient. I usually do that when it's late at night or when commuting, as it needs no brain power.

> Add the missing Javadoc, add some comments
> ------------------------------------------
>
>                 Key: DIRMINA-575
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-575
>             Project: MINA
>          Issue Type: Task
>          Components: Web Site / Documentation
>            Reporter: Emmanuel Lecharny
>
> If we except the interfaces, the code lacks of javadoc and comments, which make it complicated for new committers to get into it.
> We need to add those missing javadocs, and comments where it's necessary.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.