jettison | Highly configurable , fast JSON encoder for Go | JSON Processing library

An example of usage is below:

Kindly take note of the inner plugin dependency.

I think you question has been already answered; please, consider review this SO question.

You need to include the following dependency:

Find the solution for parallel execution with cucumber 7 and serenity junit 4. Below pom.xml is tested and working to execute parallel. According to this pom.xml to execute two ways:

1. locally - add to your runner in tags tag you want to run and then execute this command mvn clean verify

2. mvn clean verify -Dtags="@yourtagHere"

Working pom.xml:

I used the two-parameter InputStreamReader constructor as per the suggestion of @PiotrP.Karwasz and it works

I fixed this by changing

In the Oracle release notes for Java 11, I found this:

other-libs ➜ JEP 320 Remove the Java EE and CORBA Modules

Remove the Java EE and CORBA modules from the Java SE Platform and the JDK. These modules were deprecated in Java SE 9 with the declared intent to remove them in a future release (JEP 320).

The following modules have been removed from Java SE 11 and JDK 11:

If you compileInclude external resources (which is possible, but should be your last resort), unfortunately you will need to include all transitive dependencies as well. You're including jayway/jsonpath, and gson is missing. So you'll need to compileInclude gson. And as you say, when you do that, a different library is missing - so you'll need to include it as well.

That's part of the reason why this should be your last resort.

An alternative is: Check if jayway/jsonpath or gson are OSGi bundles themselves - in which case you can just drop them into Liferay's deploy folder and they'll be dynamically resolved. Of course, in this case their transitive dependencies need to be resolvable as well, so you might need to deploy a couple more bundles than just these two. But this way, all modules that use these libraries will share the same bundle.

Either way, you can inspect a bundle's MANIFEST.mf for imports to figure out what they depend on. Note: there are mandatory and optional dependencies in there. You'll need to satisfy the mandatory ones and the optional ones that you're using. If the libraries in question aren't bundles, they're managing their dependencies differently. I'd at least suggest to the project teams to OSGi'ify their packages - but that's a fix for the long run.

There's a chapter on this on Liferay's University's (free, registration required) course OSGi Basics, called "Bringing along your dependencies" (disclaimer: by yours truly), where I still like the animated special effect visualizing the option to compileInclude and what it does to file size)

I feel really silly about this now. It turns out someone uploaded something to our internal artifactory for commons-lang that was not really commons-lang. No idea how that happened, but it was a never-ending source of frustration for me. If anyone else ever sees something that doesn't make sense like this, compare the size of the jar in your .m2 folder with one downloaded directly from maven central. That would have saved me a lot of time.

The class you specified oracle.jdbc.driver.OracleDriver.

Does not implement the javax.sql.DataSource interface that is required for this org.eclipse.jetty.plus.jndi.Resource.

You have many class options, depending on your version of Oracle server installed, your version of oracle jdbc jar file, and if you have other requirements (like transactions, pooling, etc.).

Just pick the correct class for the line (that's what's wrong with your current setup)