Hi I am looking at the Toaster MD-SAL example application.
The Yang model is in: controller/opendaylight/md-sal/samples/toaster/src/main/yang When the project is built, the generated binding code is placed in: controller/opendaylight/md-sal/samples/toaster/src/main/yang-gen-sal I have looked at other projects that have Yang models, for example: controller/opendaylight/model/model-inventory/src/main/yang/opendaylight-inventory.yang In those projects the code is generated into target, which is what one would expect from Maven, for example: controller/opendaylight/model/model-inventory/target/generated-sources/mdsal-binding. I am given to understand that the Toaster is the canonical example of “how things should be done”, but it appears, at the very least, to not follow Maven conventions for generated code. That makes me suspect that it is, either, a less than perfect example, or that the ODL project has adopted different build conventions. Is there a rationale for the approach that the Toaster project has taken please? Many thanks Nathan — Nathan John Sowatskey Consulting Engineer - Programmable Infrastructure, DevOps, IoT and SDN nat...@nathan.to www.linkedin.com/in/nathandevops XMPP: nathando...@im.koderoot.net Google: nathanjohnsowats...@gmail.com Skype: nathan_sowatskey Twitter: NathanDotTo GitHub: https://github.com/DevOps4Networks http://www.kipling.org.uk/poems_if.htm _______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
