[MDSAL-752] Add Automatic-Module-Name declarations to packaged models Created: 20/Apr/22 Updated: 13/May/23 Resolved: 13/May/23 |
|
| Status: | Resolved |
| Project: | mdsal |
| Component/s: | models |
| Affects Version/s: | None |
| Fix Version/s: | 12.0.0 |
| Type: | Improvement | Priority: | Medium |
| Reporter: | Robert Varga | Assignee: | Samuel Schneider |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | Provide JPMS modules |
| Description |
|
Figure out JPMS module naming for packaged YANG modules. We probably want to use the root Java package as the name, but that needs to be confirmed. Once we have the naming figured out, update all packaged models to include Automatic-Module-Name. We really want to allow multiple revisions to co-exist: the key driver is the module name, while the secondary namespace is driven by revision – i.e. org.opendaylight.yang.gen.ietf.rfc6991.inet.types becomes org.opendaylight.yang.gen.ietf.inet.types.rfc6991. |
| Comments |
| Comment by Ivan Hrasko [ 25/Apr/23 ] |
|
So, we are going to use something like org.opendaylight.mdsal.model.ietf.rfc8345 as module name, right? |
| Comment by Robert Varga [ 13/May/23 ] |
|
So the IETF models are in org.opendaylight.ietf.inet,types,.rfc6991 module, for example. |