[MDSAL-836] Move generated YangModelBindingProvider and ResourceYangModuleInfo

Fri, 26 Jan 2024 13:47:48 +0000

We currently generate $YangModuleInfoImpl and $YangModelBindingProvider into org.opendaylight.yang.gen.v1.NAMESPACE package.

The naming of these two classes is rather unfortunate, as it starts with $ due to the requirement not to conflict with other generated classes.

At the end of the day, though, these are separate constructs. Allocate a new top-level package name to host these: org.opendaylight.yang.svc.v1, appended with the namespace, and name these YangModuleInfoImpl and YangModelBindingProviderImpl in that package.

At the end of the day:

org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.restconf.subscribed.notifications.rev191117.$YangModelBindingProvider should become org.opendaylight.yang.svc.v1.urn.ietf.params.xml.ns.yang.ietf.restconf.subscribed.notifications.rev191117.YangModelBindingProviderImpl
org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.restconf.subscribed.notifications.rev191117.$YangModuleInfoImpl should become org.opendaylight.yang.svc.v1.urn.ietf.params.xml.ns.yang.ietf.restconf.subscribed.notifications.rev191117.YangModuleInfoImplImpl

We already define the leading namespaces in yang.binding.contract.Naming, this needs to be captured there. This also will throw a wrench in assumptions around binding class -> provider/info mapping, so those need to be fixed up, too.

OpenDaylight JIRA

[MDSAL-836] Move generated YangModelBindingProvider and ResourceYangModuleInfo