[ARTEMIS-3700]: Provinding a JakartaEE 10 implementation.

[ehsavoie]

• Upgrading the API to Jakarta Messaging 3.1.0
• Updating the metadata to 3.1.0

Jira: https://issues.apache.org/jira/browse/ARTEMIS-3700

[clebertsuconic]

@ehsavoie it seems the API Is not available on maven.

Can you rebase and push -f so this gets executed again?

[ehsavoie]

@clebertsuconic it is not available until the official release (next week should be ok)

[gemmellr]

The staged spec jar was actually released so you should be able to update this now @ehsavoie

https://repo1.maven.org/maven2/jakarta/jms/jakarta.jms-api/3.1.0/

[ehsavoie]

thanks @gemmellr :)

[gemmellr]

@ehsavoie I was implicitly suggesting you rebase etc so its up to date and actually builds etc ;)

[ehsavoie]

Well there was not conflict wit the current main so i didn't rebase :) but i didn't know how to relaunch the CI.

[gemmellr]

Well there was not conflict wit the current main so i didn't rebase :)

PR commits always get rebased for artemis so its best if you do so its up to date.

but i didn't know how to relaunch the CI.

By pushing an update :)

[clebertsuconic]

@ehsavoie easiest way:

git pull --rebase upstream main
git push origin -f

if you did not have an update from main (still rebase):

git commit --amend
git push origin -f

that will update the commit ID and make the build to re-launch

[clebertsuconic]

although I was able to re-launch all jobs.. but I guess Robbie already did that anyways.

[gemmellr]

I didnt (dont have write access set up), Emmanuel had pushed when commenting about previously not.

[clebertsuconic]

@gemmellr Ohhh.. I thought he was asking to relaunch the jobs... sorry I misunderstood what he meant.. I was fast reading all my emails and I misunderstood it.. my bad.