search

jakartaee / rest

Jakarta RESTful Web Services
Other
351 stars 114 forks source link

M1 spec changes1 #1192

Closed jim-krueger closed 7 months ago

jim-krueger commented 7 months ago

First pass at changes needed to Jakarta Rest-4.0 specification.

jim-krueger commented 7 months ago

spericas, arjantijms if you concur with jansupol could you please approve this PR to allow and M1 version to be created? Thanks

spericas commented 7 months ago

spericas, arjantijms if you concur with jansupol could you please approve this PR to allow and M1 version to be created? Thanks

Don't we have until the end of January for M1? IMO we should work on this and the Javadocs more before talking about M1.

jim-krueger commented 7 months ago

Don't we have until the end of January for M1? IMO we should work on this and the Javadocs more before talking about M1.

Perhaps I am under a misunderstanding, but I thought from the Jakarta EE Platform call that the deadline for M1 was December 5th (https://docs.google.com/document/d/1DF0T2hbJqDNsY0v_lYFKCz-ZgHPbnMUIu6mhmt5LCJU/edit#heading=h.8is3kgp5ds15) and I think all other Jakarta EE specs are done.

If we truly do have until the end of January I agree, plus there are a few other changes that would be nice to include by then as well. I was assuming those would need to go into M2.

spericas commented 7 months ago

Don't we have until the end of January for M1? IMO we should work on this and the Javadocs more before talking about M1.

Perhaps I am under a misunderstanding, but I thought from the Jakarta EE Platform call that the deadline for M1 was December 5th (https://docs.google.com/document/d/1DF0T2hbJqDNsY0v_lYFKCz-ZgHPbnMUIu6mhmt5LCJU/edit#heading=h.8is3kgp5ds15) and I think all other Jakarta EE specs are done.

If we truly do have until the end of January I agree, plus there are a few other changes that would be nice to include by then as well. I was assuming those would need to go into M2.

I don't get these dates, but it seems that you are right. I'll merge this one then to get M1 "ready".

jim-krueger commented 7 months ago

Thanks @spericas. I try to attend the weekly Platform calls and will update our 4.0 Epic with pertinent information going forward.

Also, FWIW: I opened an issue in gitlab.eclipse.org and they added missing ssh public key to eclipse-rest-bot github account, which allowed me to successfully run a dry-run for the M1 apis. I think there needs to be a few more changes to create a true M1 (not a SNAPSHOT).

jamezp commented 7 months ago

I'm not sure this is the correct place for this comment, but I wasn't sure where else to put it. In the pom the jaxrs-tck module is commented out. Presumably this is because of the changes needed for new TCK tests and/or migration from @Context injection. Is there a plan to address that as well?

jim-krueger commented 7 months ago

@jamezp M1 is only spec and api. tck will come later.

jamezp commented 7 months ago

@jamezp M1 is only spec and api. tck will come later.

Thank you @jim-krueger. I had a feeling, but wasn't really too sure what the plan was :)

jim-krueger commented 7 months ago

@jamezp No problem. I believe the schedule for the TCK and a RI is early in 2024 (which might be the cause of the M1 confusion that @spericas mentioned).