assertj-core | library providing easy to use rich typed assertions | Assertion library

Acording to this answer: https://stackoverflow.com/a/51236918/16651073 tomcat falls back to default logging if it can resolve the location

Can you try to save the properties without the spaces.

Like this: logging.file.name=application.logs

The third party gradle plugin to use for jOOQ code generation isn't ready for jOOQ 3.16 yet. A fix is being discussed here: https://github.com/etiennestuder/gradle-jooq-plugin/pull/208

If the dependencies would be consumed from the users local cache $HOME/.m2/repository it could happen that parts which are already in the local cache influence the integration test. That's one of the the reasons each integration tests is completely separated from each other.

Furthermore it makes it possible to parallelise the integration tests in an easier way.

Furthermore you can configure your own settings.xml to consume any dependencies from an repository instead directly from central this would also mean that the integration test would consume their dependencies from that repo.

Apart from that the usage of the users local cache would make it impossible (or at least much more complicated) to create a local cache with predefined state (which means already existing artifacts) to test particular scenarios.

That probably works pre java 17, see How to solve InaccessibleObjectException ("Unable to make {member} accessible: module {A} does not 'opens {package}' to {B}") on Java 9?

I'm raising an issue in AssertJ recursive comparison not to use reflexion to compare AtomicReference.

Done: https://github.com/assertj/assertj-core/issues/2466

I cannot reproduce the problem because IDEA does not find the Lombok setters. Even when delegating build actions before run to Maven, I get NoSuchMethodError: '...TestEntity.setCode(java.lang.String)'. Next, I am going to try without Lombok. Please note that Lombok and AspectJ do not play nice with each other, see my answer here. Alternatively, you could also make sure that Maven does either of these:

1. First build with Javac + Lombok, then apply AspectJ binary weaving in a second step, all in one module.
2. Similar to above, but do the first build step in module A and the second one in a separate module B. Then you have an unwoven and a woven artifact, which you can both use according to your preferences. For example, you could also use the unwoven one and apply transaction aspects via load-time weaving (LTW) while starting the application. See my other answer here for both approaches #1 and #2.
3. Delombok the source code build the generated sources with the AspectJ compiler in a second build step.

I generated constructors, getters and setters in the IDE instead of using Lombok. Now the project compiles in both IDE and Maven. It behaves exactly as it should. With @Transactional, 0 entities are created, without it 2.

I am not sure if Lombok vs. AspectJ really is the problem due to non-compileability when using Lombok annotations, but it should be easy enough to try without Lombok for you. If it works in your context, too, we found the culprit and can think about implementing one of the 3 approaches mentioned above. Then you can tell me if you have any difficulty in doing so.

Update: I created the two-module version - Javac + Lombok, then Aspect weaving - for you in my fork and also issued pull request #1. I also improved testability a bit. See if that works for you.

Caveat: You cannot simply run DemoApplication from the application-lombok module, because that module is still unwoven and will not show transactional behaviour. But you can simply change the classpath for the run config to the application-aspectj module:

Update: As we found out in the comment section of the other answer, in addition to the problematic Lombok vs. AspectJ compiler configuration, the OP also simply had a problem with his IDE: Using IntelliJ IDEA Community Edition, he was first unaware of, then unable to install the AspectJ plugin, which means that IDEA does not know antyhing about the AspectJ compiler and simply overwrites anything which might have been compiled by AspectJ Maven before with plain Java classes. Therefore, transactional aspects do not work either, unless

• either pre-run compilation is disabled and mvn compile started as an additional pre-build step for the corresponding run configuration,
• or all build actions for the project are being delegated to Maven via configuration,
• the OP buys a licence of IDEA Ultimate and installs the AspectJ plugin.

It was an Intelli-J issue!

So, cleaning the Intelli-J dependency spaghetti up solved it!

1. File > Invalidate cache ... and restart. Helped a bit.
2. Closing the Intelli-J project. Then removed manually the ".idea" folder and any *.iml file.

Yes, I did option 1 previously. Especially doing action 2 solved it within a minute.

Try below and it should work

There are two separate problems from my point of view:

1. AssertJ's SoftAssertionsExtension is not yet supported by Quarkus.
2. QuarkusTestExtension does not play nicely with composed annotations.

About the latter, the issue seems to be unrelated to AssertJ. I was able to reproduce it by taking out the SoftAssertionsExtension from the custom QuarkusAssertJTest annotation and executing an empty test.

Having:

Use maven-surefire-plugin version 2.22.2 instead of 3.0.0-M5: