Use @javax.annotation.processing.Generated after moving to Java 9+

[Zegveld]

all javax modules are being replaced with jakarta, this includes @javax.annotation.Generated. This is replaced by @jakarta.annotation.Generated, allow users to choose which annotation they want on the generated classes.

(I'm also creating a PR for this.)

[famaridon]

+1

[rob-valor]

@joel-costigliola , any reason why the jakarta support doesn't get merged?

[joel-costigliola]

just lack of time, the generator is currently in a limbo state because of that ...

[scordio]

Team decision: We will start the development of the next major version with Java 17 as a baseline to better aid records and jakarta support.

[reitzig]

FWIW, in JDK 21, javax.annotation.Generated is gone so the generated assertions do not compile.

Manually replacing with @javax.annotation.processing.Generated works, of course, but that's not really what we're going for, is it? 😅 We could override all templates, I guess ...

[reitzig]

@scordio Any way we can help? We keep writing assertion classes and would much rather spend the time here. 😅

[scordio]

Hi @reitzig, I appreciate the offer! 🙂 nothing special where you could help, I'm afraid: I'm upgrading dependencies and aligning the parent POM to the latest version, which already brings a few challenges due to the custom JUnit 4 rules... once this is over, it should be possible to speed up the other topics.

I'll keep you posted.

[scordio]

Additional team decision: we will stick to @javax.annotation.processing.Generated.

[reitzig]

I was able to force v3.0.0-M3 on v2.2.0 of the Maven plugin and can confirm: this is fixed. Thanks!

[scordio]

Very cool, thanks for checking!