java8 | java8 in action | Continous Integration library

Your runtime-livedata dependency is outdated:

Those Yubico guys uses version ranges:

You can make use of split method of String class and Regex :

It's worth reading the introduction to JUnit 5. You are making a common mistake in thinking that JUnit 5 is a monolith. Rather:

https://junit.org/junit5/docs/current/user-guide/#overview-what-is-junit-5

Unlike previous versions of JUnit, JUnit 5 is composed of several different modules from three different sub-projects.

JUnit 5 = JUnit Platform + JUnit Jupiter + JUnit Vintage

Like JUnit Jupiter, Cucumber is a test engine using the JUnit Platform. Extensions are a concept from JUnit Jupiter and don't carry over to Cucumber.

Without a single example I could find in the cucumber documentation.

You'll not find anything in the main documentation until the JUnit 5 integration is feature complete. Until that time it is perfectly possible to use Cucumbers JUnit 4 integration with JUnit Vintage.

However if you're more experimentally minded you can use the documentation with the source code:

https://github.com/cucumber/cucumber-jvm/tree/main/junit-platform-engine

@CucumberOptions - there is an interface CucmberOptions which I can implement and return all required properties, but this feels like a step back from the parameterized annotation.

The Cucumber JUnit Platform integration defaults to scanning for glue and features on the class path root. If you follow the conventional maven/gradle/java project layout no additional configuration is needed.

So step definitions go in src/test/java/com/example and features in src/test/resources/com/example.

If you have a more complicated setup you should either wait and use JUnit4/Junit Vintage or simplify your setup.

This is clearly mentioned in this post

Lets walkthrough your code.

Java 11 implementation has not introduced thread-safe implementation of java.util.HashMap.

In the JDK documentation, it is clearly stated that access to Hashmap is NOT synchronized, so the behavior in a multithreaded application is unpredictable, and deadlock situation is indeed a possible side effect.

In addition, it is also said that if you want to have synchronized access, you MUST provide synchronization policy by using static method Collections.synchronizedMap, this is the piece of code to realize that:

There are two problems in your code:

1. You haven't used Locale with DateTimeFormatter which is a Locale-sensitive type. Never use SimpleDateFormat or DateTimeFormatter without a Locale.
2. You have used H instead of h for 12-hour format. The symbol, H is used for 24-hour format.

Demo:

You need to delete this line of code kapt'androidx.databinding:databinding-compiler:7.1.0-alpha01' and recompile. According to Google's open databinding document, the way to open databinding is:

Seems your hive conf is missing. To connect to hive metastore you need to copy the hive-site.xml file into spark/conf directory.

Try