Hi, There are tow aspect, one is normally we are writing javadoc to consumer who use our API. So in that case that is enough to have public/protected level javadoc. Other thing is to use source code internally to development. After sometime it will be hard to identified what is the purpose of having such impl that yourself or some one else. I believe it is better to have some detail of each possible places according to the importance and complexity of method impl and usage of variables.
*Harsha Thirimanna* Senior Software Engineer; WSO2, Inc.; http://wso2.com * <http://www.apache.org/>* *email: **[email protected]* <[email protected]>* cell: +94 71 5186770 , +94 * *774617784twitter: **http://twitter.com/ <http://twitter.com/afkham_azeez>* *harshathirimannlinked-in: **http: <http://lk.linkedin.com/in/afkhamazeez>**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122 <http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122>* *Lean . Enterprise . Middleware* On Wed, Nov 12, 2014 at 10:15 AM, Roshan Deniyage <[email protected]> wrote: > Hi Devs, > As a practice, do we include javadoc in private, protected and default > methods and variables in wso2 products? I can't identify it by looking at > the existing code since its not consistent everywhere. > > What are the rules regarding javadoc at wso2? > > Roshan Deniyage > Associate Technical Lead > WSO2, Inc: http://wso2.com > > Mobile : +94 777636406 > Twitter : *https://twitter.com/roshku <https://twitter.com/roshku>* > LinkedIn : https://www.linkedin.com/in/roshandeniyage > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
