[MDSAL-415] Generate package-info.java for model top-level package Created: 21/Jan/19 Updated: 29/Jan/19 |
|
| Status: | Confirmed |
| Project: | mdsal |
| Component/s: | Binding codegen |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Medium |
| Reporter: | Robert Varga | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Processing javadoc from our models reveals it would be useful to document the top-level package – if there is anything to document. Generate a package-info.java if there is a proper description of the module. Note this overlaps to a certain extent with *Data interface, if the module defines data. |
| Comments |
| Comment by Robert Varga [ 21/Jan/19 ] |
|
Actually, each package should have a package-info.java, referencing the snippet of yang that caused it to be generated. |