@RegisterForReflection needed on POJOS (reactive / native image)

[IvanPuntev]

Since I've updated from 3.23 to 3.28 my jackson json mappings started to break and I had to add the reflection annotation to my classes to fix it. smallrye jandex maven plugin is also included

<plugin> <groupId>io.smallrye</groupId> <artifactId>jandex-maven-plugin</artifactId> <version>3.5.0</version> <executions> <execution> <id>make-index</id> <goals> <goal>jandex</goal> </goals> </execution> </executions> </plugin>

[IvanPuntev]

May be related somehow to #50363

[sberyozkin]

@IvanPuntev Hi, creating a reproducer can help, for this discussion converted to a new issue

[IvanPuntev]

I tried to reproduce the issue by reverting the changes and removing the annotations but this time everything worked without them... I'm speculating that this could be native image build issue that happens at random / occasionally.

[IvanPuntev]

And I might be correct in some way. Digging through the logs of the build I see:
[INFO] [io.quarkus.deployment.pkg.steps.NativeImageBuildRunner] docker volume rm quarkus-native-builder-image-project-volume

Error: [io.quarkus.deployment.pkg.steps.NativeImageBuildRunner] Failed to remove volume: quarkus-native-builder-image-project-volume io.smallrye.common.process.AbnormalExitException: Process exited abnormally (pid 1623) with exit code 1 with error output: Error response from daemon: remove quarkus-native-builder-image-project-volume: volume is in use - [9df1ad299458a5e86c1afe892425c66b3114774d1088790b8e17683c09d38801] at io.smallrye.common.process.PipelineRunner.collectProblems (PipelineRunner.java:559) at io.smallrye.common.process.ProcessRunner.complete (ProcessRunner.java:165) at io.smallrye.common.process.ProcessRunner.run (ProcessRunner.java:95) at io.smallrye.common.process.ProcessBuilderImpl.run (ProcessBuilderImpl.java:199) at io.quarkus.deployment.pkg.steps.NativeImageBuildRunner.runCommand (NativeImageBuildRunner.java:133) at io.quarkus.deployment.pkg.steps.NativeImageBuildRunner.runCommand (NativeImageBuildRunner.java:150) at io.quarkus.deployment.pkg.steps.NativeImageBuildRemoteContainerRunner.rmVolume (NativeImageBuildRemoteContainerRunner.java:113) at io.quarkus.deployment.pkg.steps.NativeImageBuildRemoteContainerRunner.postBuild (NativeImageBuildRemoteContainerRunner.java:107) at io.quarkus.deployment.pkg.steps.NativeImageBuildRunner.build (NativeImageBuildRunner.java:94) at io.quarkus.deployment.pkg.steps.NativeImageBuildStep.build (NativeImageBuildStep.java:283) at java.lang.invoke.MethodHandle.invokeWithArguments (MethodHandle.java:733) at io.quarkus.deployment.ExtensionLoader$3.execute (ExtensionLoader.java:874) at io.quarkus.builder.BuildContext.run (BuildContext.java:255) at org.jboss.threads.ContextHandler$1.runWith (ContextHandler.java:18) at org.jboss.threads.EnhancedQueueExecutor$Task.doRunWith (EnhancedQueueExecutor.java:2651) at org.jboss.threads.EnhancedQueueExecutor$Task.run (EnhancedQueueExecutor.java:2630) at org.jboss.threads.EnhancedQueueExecutor.runThreadBody (EnhancedQueueExecutor.java:1622) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run (EnhancedQueueExecutor.java:1589) at java.lang.Thread.run (Thread.java:1583) at org.jboss.threads.JBossThread.run (JBossThread.java:501)

[IvanPuntev]

Probably the problem is only on my side...