odlparent references nonexistent artifacts

Found on beryllium (the master branch), pulled out yesterday.

This bug manifests during build as either "[WARNING] Could not download some/crazy/location/some-artifact.pom" warning messages or as "[WARNING] Unable to create Maven project for some:weird.artifact:pom:some.weird.version from repository." followed by org.apache.maven.project.ProjectBuildingException: Error resolving project artifact: Failure to find some:weird.artifact:pom:some.weird.version in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced for project some:weird.artifact:pom:some.weird.version".

It was tracked down to odlparent referencing nonexistent artifacts which were either moved or deleted. While it won't cause build of odlparent to break, it causes the build of other projects to break. I suspect this problem is causing the newest fixes not getting through to us, testers as the build of the artifact fails and an older build (without the fixes) gets pulled out of artifactory instead.

My current testing revealed that at least controller is rendered unbuildable by this bug, affecting clustering tests (as the clustering implementation is mainly clustered in the controller project).