Closed starksm64 closed 3 years ago
We have Jersey 3.0.0 and Tyrus 2.0.0 depending on the EJB API. Do you have any plan on pushing the API to central, so can we push Jersey and Tyrus?
To push a bit further, there is EclipseLink and Eclipse Metro that depend on the EJB API, too.
Hello @jeanouii , just a quick question, if there is anything which prevents EJB API from being promoted to maven central? Thank you.
@jeanouii and could you please take a look at #135 before sending EJB API to central?
GlassFish 6.0.0, which should be released before the Jakarta lifestream (at 8 December 2020) depends on this as well, in addition to it depending on Jersey, Tyrus, EclipseLink and Metro.
GlassFish 6.0.0, ... depending on Jersey, Tyrus, EclipseLink and Metro.
and all of those depends in turn on EJB :)
I just did the promote
`[INFO] RC-Releasing staging repository with IDs=[jakartaejb-1003]
Waiting for operation to complete... ..
[INFO] Released`
EJB is now in central :)
https://repo1.maven.org/maven2/jakarta/ejb/jakarta.ejb-api/4.0.0/
Closing as everything has been completed now.
thanks for releasing EJB :)
Now that the specification committee ballot has concluded, the following steps need to be completed by the spec team: