We've got an issue where the Jakarta EE specifications have release candidates and milestones only released to a staging repository. Given WildFly and projects that feed into WildFly would like to move forward with Jakarta EE 10 I'm proposing to release some forks, or pseudo forks as I like to call them :), of some specification API's.

You can see the status of the specifications here: https://docs.google.com/spreadsheets/d/1YTUpfdLZZrk2_UGwoX2w0seOCueRO3sQJIjWxpDAa7g/edit#gid=35969432

These pseudo forks would need to be a tag on the appropriate previous forks specification under the https://github.com/jboss organization. The artifact id and the group id would remain the same. However, the version would be x.x.x.RC-jbossorg-x. I feel the "RC" is important to denote this is not a final release. The "-jbossorg-x" is used to denote this is a JBoss Community release. These will only be deployed to the JBoss Nexus Maven repository.

Jakarta JSON Processing:

Here the specification is complete. I do not know why the artifacts are not deployed. However, we'll need to fork the API and RI.

Jakarta JSON Binding:

Same as above. The specification is complete and the artifacts are not deployed. We'd also need to fork the API and RI.

Jakarta RESTful Web Services:

This just recently went for a re-vote due to a TCK challenge that was resolved. The vote doesn't end until April 6th.

--