Java

With Gradle, very little comes out of the box and a lot of the filtering and configuration you need to do on your own. That can be confusing at first especially as a beginner and even more so if you are accustomed to Maven.

Log hierarchy in Logback is based on the log names. That is a characteristic that makes lots of interesting and handy features possible. The post looks into a couple of examples how that works. How named log hierarchy works According to the logger documentation, a logger is said to be

Since version2.16.3 [https://github.com/mockito/mockito/pull/1221]Mockito has official support for Junit5. Using Mockito with JUnit now is even easier than before. Previously I kept forgetting what rule I was supposed to use for injecting the mocks, and how I set the strictness again? Plus

This is a very short example of how you can use RESTEasy to send JSON requests. For one of my pet projects, I needed to send requests to my JSON based API. I usually use Apache‘s HttpClient for simple requests. But, this time I wanted to try some of

JUnit 4 extension model is a bit scary. You have @Rule, @ClassRule, and different Runner implementations. Very often you need to use all of them at once. On top of that you will probably end up with multiple rules that you will need to chain properly. Doable, but scary for

I recently needed to access some of the pom properties at runtime. To be more specific, I needed the version related properties: artifact id, group id, and version. It turned out that there are at least three ways do that.