|
Sorry, this may have sounded confusing. The short name change is great before the release, the infrastructure (github, CI,...) changes after the release. Unless that contradicts each other.
-- Jan
From: jaxrs-dev <jaxrs-dev-bounces@xxxxxxxxxxx> on behalf of Jan Supol <jan.supol@xxxxxxxxxx>
Sent: Sunday, November 28, 2021 9:58 PM
To: jaxrs developer discussions <jaxrs-dev@xxxxxxxxxxx>
Subject: Re: [jaxrs-dev] [External] : Re: Jakarta REST 3.1.0
Hi Arjan,
Thank you for stepping up and being willing to perform the changes. If I can speak for me only, I'd prefer to go ahead with the changes AFTER the Jakarta EE 10 release, so that the release is not blocked by any potential issue with the infrastructure. Jakarta
REST 3.1 finishes with the late changes mainly on the TCK side, to be ready for the ballot asap.
Thanks,
Jan
From: jaxrs-dev <jaxrs-dev-bounces@xxxxxxxxxxx> on behalf of arjan tijms <arjan.tijms@xxxxxxxxx>
Sent: Sunday, November 28, 2021 6:17 PM
To: jaxrs developer discussions <jaxrs-dev@xxxxxxxxxxx>
Subject: Re: [jaxrs-dev] [External] : Re: Jakarta REST 3.1.0
Hi,
Those paths and CIs and job names and what have we can all be changed without doing PRs, which is what I referred to above. I've done this for multiple projects in the past.
The move from github/eclipse-ee4j to github/jakarta is a small (but worthwhile) complication, otherwise it would be truly trivial. When is the move planned for? It has been on the agenda for over 2 years now, and would be good to finally execute it.
I see. Chaning the SHORT NAME is absolutely ok for me. Please do not change the Github URL to not confuse
people again (and again and again) unless absolutely necessairy. Having said that, if the EF replaces the group path eclipse-ee4j/* anyways to jakarta/*, it certainly is OK for me to go with the path jakarta/rest instead of jakarta/jax-rs in the same step.
-Markus
Von: jaxrs-dev [mailto:jaxrs-dev-bounces@xxxxxxxxxxx]
Im Auftrag von Jan Supol
Gesendet: Sonntag, 28. November 2021 11:38
An: jaxrs developer discussions
Betreff: Re: [jaxrs-dev] [External] : Re: Jakarta REST 3.1.0
just to be sure, you are -1 for renaming the project. The project name is Jakarta RESTfull Web Services, that's not gonna change.
The change is about a short name, which you are +1 for using Jakarta REST.
Now for the GitHub repo, we use jaxrs-api. Are you ok with moving it to rest-api (after moving the repo from eclipse-ee4j to some
jakartaee org which happens anyway)? That's what I understand was Ed's email about.
I wonder how you want to change the spec title without a PR.
-Markus
Von: jaxrs-dev [mailto:jaxrs-dev-bounces@xxxxxxxxxxx]
Im Auftrag von arjan tijms
Gesendet: Samstag, 27. November 2021 15:21
An: jaxrs developer discussions
Betreff: Re: [jaxrs-dev] [External] : Re: Jakarta REST 3.1.0
Hi,
Let’s not do a PR then, and the problem is solved.
On Saturday, November 27, 2021, Markus Karg <markus@xxxxxxxxxxxxxxx> wrote:
No we didn't. Please check the rules we gave us
https://github.com/eclipse-ee4j/jaxrs-api/wiki/Committer-Conventions. There must be zero minus ones.
-Markus
Von: jaxrs-dev [mailto:jaxrs-dev-bounces@xxxxxxxxxxx]
Im Auftrag von arjan tijms
Gesendet: Freitag, 26. November 2021 23:00
An: jaxrs developer discussions
Betreff: Re: [jaxrs-dev] [External] : Re: Jakarta REST 3.1.0
Didn't we just do a yes/no vote, with a simple majority?
To sum up, there is one binding -1 vote from a committer, which means that the name will not get changed.
-Markus
Von: jaxrs-dev [mailto:jaxrs-dev-bounces@xxxxxxxxxxx]
Im Auftrag von arjan tijms
Gesendet: Freitag, 26. November 2021 20:01
An: jaxrs developer discussions
Betreff: Re: [jaxrs-dev] [External] : Re: Jakarta REST 3.1.0
Hi,
Summing up, I think we have a majority vote for Jakarta REST, so shall we go ahead and make that official?
We had a similar issue with Jakarta Faces, which accidentally got named Jakarta Server Faces for a short while. It was fairly easy to correct that. There too, having Jakarta Server Faces as an official name and then Jakarta Faces as the real name simply didn't
add anything for anyone.
Additionally, with having simple names (Jakarta Faces, Jakarta Transactions, Jakarta Persistence, ...) people don't feel the need to start using cryptic abbreviations. Cryptic abbreviations are very unfriendly to new people, so best avoided.
Projects generally have a full name and a short name. Currently, Jakarta RESTful Web Services has a short name, restful-ws. This name first appears (to me) about the time we were getting RESTful web services 2.1
ready for ballot (Jul-Sep 2019).
I'm +1 on moving away from JAX-RS since that's fading further and further in the rear-view mirror.
I'm supposing we aren't interested in changing the package name -- sticking with
jakarta.ws.rs. In a perfect world, I think it would be nice if the repository and package name lined up but, that seems in-opportune right now (i.e. repository were to become restful-ws and the package name were to change to jakarta.restful_ws or
jakarta.restful.ws. (or replace restful with rest, etc.)
If this is the direction the group decides to go in, we should update the name of the GitHub repository as well as the name of the PMI project page (currently
https://projects.eclipse.org/projects/ee4j.jaxrs). For me, getting the PMI project page, the repository, and it's associated web-page all aligned with the 'short-name' that the Spec. directory uses would be nice. I don't see this as something super urgent
though.
To recap:
I am certain all the jaxrs names are just hold-over legacy. The team can decide if it wants to use 'rest' or 'restful-ws' or anything else that can be consistently applied. Maybe the 4.0 release is the right time
for doing this.
-- Ed
On 11/23/2021 9:49 AM, Markus Karg wrote:
I do not see the confusion. IMHO most people are able to understand that "Jakarta REST" simply is a short from of "Jakarta RESTful Web Services".
-Markus
Von: jaxrs-dev [mailto:jaxrs-dev-bounces@xxxxxxxxxxx]
Im Auftrag von Santiago Pericasgeertsen
Gesendet: Montag, 22. November 2021 15:29
An: jaxrs developer discussions
Betreff: Re: [jaxrs-dev] [External] : Re: Jakarta REST 3.1.0
I am -1 for actually renaming the project, but I am +1 for adopting "Jakarta REST" as the official short form we commonly use in our documents.
That is basically the status quo. It simply adds confusion when we mostly refer to it as “Jakarta REST” and the project is named differently.
_______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jaxrs-dev__;!!ACWV5N9M2RV99hQ!Zd3vPPFpRlyLUxuOCo_zf5zDz7V3QNJd4MU7gQNXwITaUZwnlCb5HvSdK09pR1Q$
_______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jaxrs-dev
_______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jaxrs-dev
_______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jaxrs-dev
|
