commons-math | Miscellaneous math-related utilities | Math library

Information about transitive dependencies isn't included in Your jar. When You publish libraries to a repository via Maven or Gradle, there are several files being published:

• obviously .jar file with all compiled code
• pom.xml file (it contains transitive dependencies definitions)
• some files with checksums

When You just copy Your library jar to lib directory, Your application has no information about it's dependencies. There are several solutions:

1. Publish Your library to Maven Repository (Sonatype Nexus or JFrog Artifactory are most popular products to set up self hosted repository, but You can also use mavenLocal()) instead of copying jar to lib - I think it's the best solution

2. Build library as fatJar (jar file with compiled code and all it's dependencies - Creating a Fat Jar in Gradle)

3. Copy all of Your library dependencies to lib folder

You did not provide the type of publication, so you use just a basic Publication. from() is a function of MavenPublication, so you need to explicitly specify that you need a MavenPublication:

I was able to sort the above issue and few other ClassNotFoundException by copying the following jar files from extlib to lib. Both folder are in oozie_install/oozie-5.2.1.

• libext/hadoop-common-2.6.0.jar
• libext/commons-configuration-1.6.jar
• libext/hadoop-mapreduce-client-core-2.6.0.jar
• libext/hadoop-hdfs-2.6.0.jar

While I am not sure how many more jars need to be moved from libext to lib while I try to run an example workflow/job in oozie. This fix brought up Oozie web site at http://localhost:11000/oozie/

I am also not sure why Oozie doesn't load the libraries in the libext/ folder.

This might have to do with you not using Generics with your java Collections

You are missing the vertx-web as a dependency.

To fix the compilation issues you need to add:

I can see org.springframework.boot.cli.app.SpringApplicationWebApplicationInitializer in the stack trace. That class is part of Spring Boot's CLI and shouldn't be involved when you're building an application with Maven or Gradle. Looking at your pom, I can see the following dependency:

Well the correct term is that @EnableAuthorizationServer is in maintenance mode which basically means deprecated. As in there will be no added features or updates.

The story goes basically as follows.

During Spring 4 i believe there was a single person that maintained the oauth2 part of spring security. When Spring security 5 was launched the team at pivotal decided to do a major overhaul of spring security and the oauth2 parts. So what they did was to drop Authorisation server support, and instead focus on the Resource server support at first.

Spring announcement of dropping Authorisation server support

You have pulled in spring-cloud-starter-oauth2 which in turn har a peer dependency on spring-security-oauth2-autoconfigure which in turn pulls in spring-security-oauth2.

Here Spring clearly states that if you wish to use spring-security-oauth2 they will help you out, but it is in maintenance mode.

The choice to not support it was made because an authorization server is like owning a product. Spring doesn't maintain their own database, or own Ldap server etc. There are plenty of auth servers out there that can be used, okta, curity, github, fb, google, etc, etc.

But Spring has actually reevaluated that choice and decided to start a community developed open source authorisation server

So you have 3 choices:

• use the old, that is in maintenance mode
• use a 3rd party vendor, github, fb, google, okta, curity etc.
• try out the new open source authorisation server

Nowadays almost all plugins for Gradle are published to the Gradle Plugin Portal, so Gradle knows how to resolve them and you can simply use the plugins block to define them in your build script: