yangtools | Mirror of the OpenDaylight yangtools gerrit project | iOS library

Beryllium is staggeringly old by ODL standards. It hasn't been supported upstream for many years. Please use a recent version of ODL.

https://docs.opendaylight.org/en/latest/downloads.html

org.opendaylight.mdsal.maven.sal.api.gen.plugin.CodeGeneratorImpl is incorrect - it should be org.opendaylight.mdsal.binding.maven.api.gen.plugin.CodeGeneratorImpl.

However you are deriving your pom from binding-parent so you don't need to re-define the yang-maven plugin at all as it is already defined/provided by binding-parent.

Looks like a version incompatibility - you're referencing yang-maven-plugin version 2.0.8-SNAPSHOT, which is the current unreleased master branch, and dependency maven-sal-api-gen-plugin version 0.7.4-Lithium-SR4, which was like 5 major releases ago and long obsolete.

E.g. https://stackoverflow.com/a/47069510/421602 lists the version numbers you can use for the opendaylight-startup-archetype. You can indeed also just check the repository, but the correct link to see all versions of that archetype would be https://nexus.opendaylight.org/#nexus-search;quick~opendaylight-startup-archetype (not yangtools-artifacts).

As for confusion re. versions in feature.xml and the pom.xml files, the best is to either look at the archetype example projects, or find the right version by looking at the appropriate branch in the OpenDaylight source code. For example, if you wanted to know what the correction version of say l2switch for ODL's Carbon release was, you could have a look at e.g. https://github.com/opendaylight/l2switch/blob/stable/carbon/artifacts/pom.xml to find 0.5.3-SNAPSHOT (or use 0.5.2).

FYI: As far as I know the archetype for the Nitrogen release is broken at the time of writing this; so I would just use the latest bleeding edge Oxygen, for the archetype and projects like l2switch or whatever you are interested in.

Notice that the error indicates namespace http://karaf.apache.org/xmlns/features/v1.4.0 which is for karaf 4.x which was introduced in the Opendaylight Nitrogen. However your features xml has namespace http://karaf.apache.org/xmlns/features/v1.2.0 which indicates you're using Opendaylight Carbon or earlier. So that means you're pulling in a features repository from Nitrogen (eg dluxapps or openflowplugin) - in the pom make sure you specify the correct dependency versions for dluxapps, openflowplugin etc for the Opendaylight version you're using (I assume Carbon).

The problem re. maven-javadoc-plugin seems to be due to "error: unknown tag: author:" - that's fixed by https://git.opendaylight.org/gerrit/#/c/66268/. (FYI the JavaDoc output can be a bit confusing; it's only the lines where there is an "error: " at the end that cause the build to fail; all lines starting with [ERROR] but ending in "warning: " do not.)

The REAL question is why you hit this locally when this works for everyone else and on the ODL Jenkins build... The reason for that is if we note your C:\Program Files\Java\jdk-9.0.1\... you appear to be building ODL on Java 9 - and that is not supported, yet! I've just proposed https://git.opendaylight.org/gerrit/#/c/66269/ to avoid similar problems for others in the future (until we're ready). Until then, please both build and run ODL only with Java 8 and you will have a lot less problems.

PS: I was not crystal clear if you've fully resolved your first problem re. karaf-maven-plugin, and are now only asking about your second problem re. maven-javadoc-plugin - it's best to remove from your question what you have resolved, or open separate new questions for new things you run into. But the karaf-maven-plugin could very well have issues when running the build under Java 9 as well.

Have you read the ODL Eclipse Setup FAQ, and tried all tips there?

For example, the custom Maven settings.xml which is required for it to download artifacts from http://nexus.opendaylight.org is automatically configured, but the very first time you need to restart Eclipse once.)

Do not touch any of the pom.xml - it should just work out-of-the-box, because in ODL CI all of these projects (like controller/benchmark/dsbenchmark) of course do build just fine.

Are ALL of your projects in Eclipse red, or just some?

In the logs you provided: