The sal-binding-dom-it project has errors when imported into eclipse as a result of the yang files not being generated because the "*it" projects don't build from the top-level via CLI - they're activated by a maven profile. Unfortunately, eclipse ignores the maven profile exclusions on import. Enabling the yang-maven-plugin to run in eclipse which fixes the error.

The new nagasena projects also cause errors. They use a zip maven plugin to unzip the openexi party jars under target and re-build it as a bundle. For the bundles that import nagasena as a dependency, if the nagasena project is imported, eclipse wires it to target-ide instead of the jar file in the maven repo. However, the truezip plugin doesn't run in eclipse so the classes aren't under target-ide, thus the compile errors. Removing the project or not importing nagasena fixes the errors b/c eclipse then resolves the classes from the maven repo jar. We can fix this by putting the openexi jars on an external repo, maybe the opendaylight nexus. Then change the nagasena project to "bundle-ize" it using Embed-Dependency.