Change project name to Jakarta Annotations

Question

Change project name to Jakarta Annotations

Closed this issue 5 years ago · 9 comments

ivargrimstad commented 5 years ago

Background information:
https://waynebeaton.wordpress.com/2019/04/04/renaming-java-ee-specifications-for-jakarta-ee/

Checklist:

GitHub
README file
CONTRIBUTING file
Eclipse Project under https://projects.eclipse.org/projects/ee4j

Answer 1 · 2019-04-26T07:36:24.000Z

How about skipping Common and use Jakarta Annotations?

Answer 2 · 2019-04-26T13:13:31.000Z

Yeah sounds good. I will try to take a crack at these changes on the weekend.

Answer 3 · 2019-04-26T13:28:20.000Z

Jakarta Annotations would make me think that this includes all annotations used in Jakarta, whereas Jakarta Common Annotations makes it clear that these are annotations used in more than one place.

Answer 4 · 2019-04-26T14:19:35.000Z

... Fair point.

Answer 5 · 2019-04-29T19:21:14.000Z

I think Jakarta Annotations is fine, and it avoids the possibility of another "JCA" acronym.

Answer 6 · 2019-06-05T21:04:12.000Z

For the Github project name change, do we need to keep the -api suffix?

Answer 7 · 2019-06-05T21:55:33.000Z

We're going to end up with a number of GitHub repositories associated with a project.
We might have annotations-spec, annotations-api, annotations-tck, for example.
Perhaps one of them should drop the suffix. I would argue that that should probably
be the specification project, which would result in a cleaner GitHub pages URL at
which to host the web site with all the information about the project.

Answer 8 · 2019-06-05T22:34:56.000Z

makes sense!

Answer 9 · 2019-06-06T20:06:21.000Z

Take a look at the associated PR for the exact wording I've come up with and comment.