search

jakartaee / common-annotations-api

Jakarta Annotations
https://eclipse.org/ee4j/ca
Other
53 stars 40 forks source link

Change project name to Jakarta Annotations #34

Closed ivargrimstad closed 5 years ago

ivargrimstad commented 5 years ago

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

Checklist:

ivargrimstad commented 5 years ago

How about skipping Common and use Jakarta Annotations?

rotty3000 commented 5 years ago

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

Cousjava commented 5 years ago

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.

rotty3000 commented 5 years ago

... Fair point.

bshannon commented 5 years ago

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

rotty3000 commented 5 years ago

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

bshannon commented 5 years ago

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.

rotty3000 commented 5 years ago

makes sense!

rotty3000 commented 5 years ago

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