Javadoc

RE: Javadoc

2014-02-06T14:56:56Z

Hi Adam,

We absolutely encourage community involvement with our API documentation (e.g, Javadoc). We have a public project in JIRA called LRDOCS where we track API documentation tickets. Let me give you a brief list of proper steps to take for submitting Javadoc.

Create an LRDOCS ticket for the Javadoc you plan to submit. Once you've submitted your Javadoc, assign that ticket to the person you submitted it to. This will enable Liferay to track your submission, preventing it from getting lost in the mix.
Liferay's Javadoc adheres to the Javadoc Guidelines. This should be referenced to make Javadoc submissions consistent to what we already have.
We submit Javadoc through Github pull requests. Please send your Javadoc submissions to @codyhoag in the liferay-portal repository.

Let me know if you have any other questions.

RE: Javadoc

2014-02-05T20:37:54Z

Is it feasible to include community submissions in the API documentation process?

I know that there are people out there who want to contribute their findings about fringe methods/parameters and behaviors in a way that won't get lost in the noise of the community forums, blogs and wikis.

(I'm one of those people)

RE: Javadoc

2014-01-23T15:14:13Z

Hi D.U.,

Liferay has put a heavy emphasis on producing more Javadoc for the coming year. Of course, as you stated already, there are many classes/methods with no Javadoc; so this will not be an overnight transformation. However, I've spoken with several Liferay developers that are willing and dedicated to providing Javadoc for their areas of expertise. You can view the public LRDOCS project to view ongoing Javadoc work, vote up Javadoc tickets, or create tickets for Javadoc classes/methods you'd like to see documented.

Javadoc

2014-01-23T14:40:35Z

What is the reason that most of the Liferay classes/methods have no Javadoc?
For instance, DLFolderServiceUtil.addFolder(...)
Not a single character of Javadoc can be found. I wanted to know what the boolean parameter mountPoint is for.
It is disappointing that the Liferay developers do not have a well programming manner. I know that a lot of programmer don't like to document their code but this is as important as the code itself.
When will the API be fully documented? Maybe the programmers should be teached better to do so. What about QA at Liferay? Is there any at all?

Another point: Abuse of programming constructs
For instance, DLAppLocalServiceUtil.getFolder(...)
Here is a Javadoc existent but exceptions are used to control the flow. Instead of returning a Folder object if any could be found or null if not, the method raises a PortalException if the folder can not be found. This makes the code around nasty and it is no good programming practice.