You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2026/05/30 07:13:00 UTC
[jira] [Commented] (OFBIZ-9148) Check and enhance the Javadoc rules/documentation for the project
[ https://issues.apache.org/jira/browse/OFBIZ-9148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18084498#comment-18084498 ]
ASF subversion and git services commented on OFBIZ-9148:
--------------------------------------------------------
Commit 2a67005740af3a871ccacf4f4f57644d4a878a5e in ofbiz-plugins's branch refs/heads/release24.09 from Jacques Le Roux
[ https://gitbox.apache.org/repos/asf?p=ofbiz-plugins.git;h=2a6700574 ]
Improved: Check and enhance the Javadoc rules/documentation for the project (OFBIZ-9148)
Remove useless </p> that generates errors: unexpected end tag: </p>
Those are a bit different than those fixed in previous commit.
The indentation is 5 spaces not 4. I decided to not change that, just removing
the </p>
(cherry picked from commit a52f9fb2dcb085125cf3845efd11f3d287fc022a)
> Check and enhance the Javadoc rules/documentation for the project
> -----------------------------------------------------------------
>
> Key: OFBIZ-9148
> URL: https://issues.apache.org/jira/browse/OFBIZ-9148
> Project: OFBiz
> Issue Type: Improvement
> Components: Confluence
> Reporter: Michael Brohl
> Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: javadoc-100-warnings.txt, javadoc-12168-warnings.txt
>
>
> We are currently working on a huge amount of invalid Javadoc entries in our codebase. We'll have to check if we already have some documentation on how to writer proper Javadoc and how to avoid the biggest mistakes and maybe enhance it.
> We also have to check the Javadoc during review of contributions and should ask for creation or correction of proper Javadoc just like we do with code.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)