[
https://issues.apache.org/jira/browse/OFBIZ-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545121
]
Skip Dever commented on OFBIZ-1387:
-----------------------------------
I too agree with Adrian's method because it puts the comments in two easy to
get at places. Javadocs or types like this are great ways to document stuff.
Jonathon wrote:
"Codes could have low-level docs for coders, we could add those, yes. But
frankly, if a coder has gone that deep into OFBiz codes, he is already prepared
to walk the codes himself, and wouldn't complain that there are no docs!"
Jonathon, I agree, but what about the next guy to come alone. How much wasted
man-power does it take walking through the code before someone realizes how
this wasted time could be put to better use. It is my view that if someone
commits a Javadoc entry in the code, that commit should be reviewed and added
pronto (maybe with a change log at the top indicating that no code has been
changed for those like me who are paranoid about adding changed code without a
serious beta test.)
> comment Entities
> ----------------
>
> Key: OFBIZ-1387
> URL: https://issues.apache.org/jira/browse/OFBIZ-1387
> Project: OFBiz
> Issue Type: Task
> Components: accounting, content, ecommerce, framework, humanres,
> manufacturing, marketing, order, party, pos, product
> Reporter: BJ Freeman
> Assignee: Adrian Crum
> Attachments: party_entity_model.patch
>
>
> comment the Entities files in the entitymodel.xsd
> put a comment in this jira of the entities you are going to comment
> when you attact your patch number it with a date, so if you don't do the
> whole thing someone else can add to it, and not overwrite your patch.
> hope the committers don't mind this break in the rules.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
