Skip to content

compiler: add option @generated=jakarta #12077

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 3 commits into from
Closed

Conversation

Hc747
Copy link

@Hc747 Hc747 commented May 18, 2025

Add (optional) support for @jakarta.annotation.Generated while retaining existing functionality.

An extension of #11086 and continuation of #11215.

@ejona86
Copy link
Member

ejona86 commented May 20, 2025

It is not at all clear what problem this is trying to solve. In #12080 I'm disabling the third-party generated annotation. If we do need a new annotation, we'd want to own it, as with javax.annotations' removal from Java 9 there is not a general-purpose annotation to use for this purpose.

@Hc747
Copy link
Author

Hc747 commented May 20, 2025

There is and it's Jakarta.

@ejona86
Copy link
Member

ejona86 commented May 20, 2025

@Hc747, if you were trying to communicate something, it failed. I have no clue what you are talking about. I understand Jakarta is a thing and exists, but why is it relevant? If this is not done, what burden does it cause you?

@Hc747
Copy link
Author

Hc747 commented May 21, 2025

Jakarta annotations are 1:1 with javax annotations - it's literally just a different namespace due to legal reasons. Without the ability to support Jakarta we lose feature parity with javax and integration with tooling that identifies @Generated code via annotation.

@Hc747 Hc747 closed this May 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants