mock-api | TestAPI is a fake online REST API | Mock library

You have to use the information SLF4J provide you and back trace the dependency using dependency:tree and its includes option.

This message:

Try to update this line

I solved that though adding code under line. But I can't understand what was cause.

You have forgotten to add @RunWith and specify the PowerMockRunner

If you are able to use Junit-4 this is the solution.

Looks like you need to add -Djdk.attach.allowAttachSelf=true

See https://github.com/powermock/powermock/issues/979#issuecomment-485678666

Installed Oracle JDK 1.8.0_281-b09

Few things

1. One of the computer isn't compiling the code with Java 8, otherwise jaxb would be available

2. Unless you're maintaining old code, you should be using Java 11 at a minimum

3. If you absolutely need Java 8, it's best to migrate to OpenJDK rather than Oracle's distribution

And if it's a brand new project, you can use any newer Java version, but worth pointing out that Spring Boot version should also be newer

Your problem here is you are trying to install the json-server dependency in a multi-stage container build, which means you can run related commands on that stage alone.

In order to get around this, you will need to move the package installation directly on your second stage so it can be accessed for running commands:

And that prints -> Central European Standard Time

Why are you doing this? "Calendar" as an API is broken and obsolete, do not use it. 'Central European Standard Time' is a weird concept that probably you don't want at all. It is a broken concept you need to get rid of.

The EU has already decided that the EU as a whole is going to ditch the concept of daylight savings time entirely, but there is no actual requirement for each EU country to go to the same time zone. This means a few things:

1. It's always been an idiotic standard; There is 'Central European Standard Time' (UTC+1), and 'Central European Summer Time' (UTC+2), which both shorten to CEST, but in common parlance, 'CEST' means summer time (UTC+2), and 'Central European Standard Time' is shortened to CET. Facepalm moment.

2. Both of these zones are going to mean something completely different soon. At best, we'll be left with 'Central European Time' (CET), but that may actually end up being UTC+2, so 'CET' now refers to UTC+1, but next year it may be reinterpreted to mean UTC+2, which is hell for computers, so the best option is not to buy into this CET/CEST malarky in the first place. Whichever one isn't chosen will then be an obsolete relic: A zone that no country is actually in.

3. Maybe CET/CEST will disappear entirely: Maybe western european countries adopt UTC+1, whereas eastern ones adopt UTC+2, to match their longitudes. In a vacuum, Poland should adopt UTC+2, The Netherlands should adopt UTC+1. Then there is no 'european central time' whatsoever.

4. You already HAVE the right answer in your code: Europe/Berlin. That is how you name time zones. Not with 3-letter or 4-letter acronyms that are nebulous, overloaded, and insufficient.

But in all cases the changes are overwritten and I get UTC when calling and endpoint.

That's the problem with global defaults. 'Do not use singletons' is a common maxim, and this is why: You run into deep problems.

Yes, something is overwriting it.

The best fix is that you shouldn't need to care what the 'global' timezone property is. Whatever code you have now that uses Calendar? Find it, replace it with code based on java.time.

reference: The deprecation notice on TimeZone's javadoc about TLA time zone IDs.

"Could not find artifact com.amazonaws:aws-java-sdk-bom:pom:2.15.4 in central"

To address this POM issue, please refer to the AWS Spring BOOT example applications that are located in https://github.com/awsdocs/aws-doc-sdk-examples/tree/master/javav2/usecases.

They all work and use AWS SDK For Java Version 2. I have deployed every one of them to the Cloud by using Elastic BeanStalk. Furthermore, these Spring Boot example apps interact with different AWS services like DynamoDB, Amazon RDS, Amazon S3, Amazon SES, Amazon Rekognition, etc.

• Creating your first AWS Java web application

• Creating the DynamoDB web application item tracker

• Creating the Amazon Relational Database Service item tracker

• Creating an example AWS photo analyzer application using the AWS SDK for Java

Once you are successful getting the apps to work using V2, then you can build some tests