http-share | Quickly share directories over http | HTTP library

The class you are searching for is included in maven's installation directory.

Full path is

MAVEN_INSTALLATION_DIR/lib/wagon-http-$VERSION-shaded.jar

Note that $VERSION depends on Maven's version you have installed.

Edit: Classes source code can be found here. You have stated in comments that source's and jar's class package differs. That's partially true, but this is explained by checking artifacts wagon-providers artifact's pom.xml.

Especially you should check configuration of Maven-shade-plugin.

Here artifact wagon-http-shared is included in the build process and here its package in the produced jar is changed.

Finally get the test running. I've excluded all libs with duplicated classes:

The key problem here is that you either don't have OpenCV SDK installed on your host machine or wrongly refer to the SDK in the project. The steps are as follows:

• once you got the project imported in Android Studio navigate to the app's build.gradle file to check the version of OpenCV used in the project which is 2.4.13.3;
• now go to the OpenCV's download page and download the 2.4.13.3 archive. Unpack it once downloaded;

• navigate to project/app/src/main/jni/Android.mk and specify the path to the OpenCV sdk installed in the following way:

Since you're using Jetty you should be adding spring-cloud-starter-contract-stub-runner-jetty - that way the started WireMock will use the proper container.

(Damn I cannot comment till I have 15 rep.)

It could be you don't have jBPM dependencies in your project. In such case I think Drools uses a dummy provider for processes that has no capabilities. But I am not 100% sure about this.

I have a work around for this issue. Even eclipse has the same issue like this as per my colleague.

Create a testng suite file testng-developer.xml

If you can not fix your current problem, you can try other deployment mechanisms like maven Artifactory plugin or deploying from CI. In one of Artifactory's blog posts it is advised to deploy from Jenkins(or other CI in non-cloud environments) to aquire cleaner pom.xml's. https://www.jfrog.com/confluence/display/RTF/Maven+Artifactory+Plugin https://jfrog.com/blog/dont-let-maven-deploy-plugin-trip-you/

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.

So, you really need only one version of the el jar. And it should be: