javawriter VS Mockito

javapoet (for generating code in Java): square/javapoet: A Java API for generating .java source files. (github.com)

Resources: 1. Spring Boot Official Documentation on configuring multiple data sources: Spring Boot Reference Documentation 2. javapoet (for generating code in Java): square/javapoet: A Java API for generating .java source files. (github.com) 3. Guide to Annotation Processing in Java: Java Annotation Processing and Creating a Builder | Baeldung

Javapoet. This helped me a lot, because i wrote two generators, one for one employer, who don't like dynamic generators, so the first was to generate mappers like mapstruct does; from model to pojos and viceversa. The second one was a static testing pojo factory generator; this last one i made public (it's pretty basic and now we have projects like instancio and podam) its name is mother-factory.

> can you show an example of how you'd parse, say, a .java.in

The canonical way to do such a thing is through the java annotation processing api [1] and using a tool like java poet [2]. Before you did that, you'd probably decide if you wanted to instead use bytecode generation with a library like bytebuddy [3]

But, assuming for some reason, you wanted to torture yourself and actually consume a java.in file and apply a regex, then you'd probably pull out the "maven-replacer-plugin" [4] and configure that for the task at hand. (or use your favorite templating language plugin. There's a million of them).

Though, to be fair, this really isn't something that comes up in regular java programming due to the nature of the ecosystem. Anything you'd want to codegen likely already has a library and anything you didn't would receive (legitimate) push back.

[1] https://www.baeldung.com/java-annotation-processing-builder

[2] https://github.com/square/javapoet

[3] https://bytebuddy.net/

[4] https://github.com/beiliubei/maven-replacer-plugin

I’ve used a maven archetype before with velocitemplate. That solution was iffy so we then migrated to using https://github.com/square/javapoet to generate the java source and write it to the desired files. I think we also used the google formatter library so the files would be formatted after generating.

JavaPoet

Mockito 5 Released (1 min)🎉 https://github.com/mockito/mockito/releases/tag/v5.0.0

For those using a "release" testBuildType for integration tests, what does your mocking setup look like? My app is stuck on Mockito 2.23.4, because higher (> 1.8.12) versions of Byte Buddy required beyond that point [do not play nicely with non-debuggable APKs](https://github.com/mockito/mockito/issues/2302). Solutions I've considered so far:

Mockito

The code is pretty self explanatory but here's a quick run down. o.getClass().getDeclaredFields() gets us an array of all the fields. We then have a enhanced for loop that loops over the array. Check if the field is annotated field.isAnnotationPresent(Gucci.class). If it is then we set its modifier to true with field.setAccessible(true);. If we don't do this and the field is private we will get an error. Then we get the binary name of the field, field.getGenericType().getTypeName();, remember its just the package and the class name. Lastly we set the value of the field, field.set(o,dynamicInjection(classLoader,binaryName). With that we have now created a dependency injection annotation with the Junit 5 extension model. Now I am sure you can see the tower of exceptions, which is obviously not ideal. I'm not sure how I want to handle all the exceptions yet. However, I will be digging around the Mockito code base to see if I can find how they handle all their exceptions.

Mockito 3.11.* releases

Hi, I've been trying to write parquet files on android for the past couple of days, and have really been struggling to find a solution. My original hypothesis was to just use the java parquet implementation (https://github.com/apache/parquet-mr), but I've since realized that not all java libraries play well with Android. I've gone through essentially dependency hell trying to franken-fit the library into my project, and imported as much as i could before hitting walls such as this one (https://github.com/mockito/mockito/issues/841).