9:23 a.m.
On 3/25/22 1:05 PM, James Perkins wrote:
Hello All,
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_UGwoX2w0seOCueRO3sQJ...
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.
The two JSON reference implementations forks I'm not sure how to
handle yet. Since we do not have previous forks of these, releasing
these is not as straightforward. Before the JSON API's/RI's are
released as a fork, I'll send an email to the specification list
seeing when we can expect a real release.
I just opened https://github.com/eclipse-ee4j/jpa-api and forked to
https://github.com/jboss, then renamed https://github.com/jboss/jpa-api
to jboss-jakarta-jpa-api (following naming pattern of other similar SPEC
API forks).
If we already had already previously created a `jboss-jakarta-jpa-api`
fork, I would of just synced with the upstream (as needed).
As a further step, I now would like to create Persistence 3.1
`x.x.x.RC-jbossorg-x` based on
https://github.com/jboss/jboss-jakarta-jpa-api/commit/a36e492b0697cf260c1...
from branch
https://github.com/jboss/jboss-jakarta-jpa-api/tree/3.1-3.1.0 which I
will do on a new branch `3.1.0-3.1.0.RC-jbossorg-x`.
Scott
Does anyone have any objections or concerns with this?
--
James R. Perkins
JBoss by Red Hat
_______________________________________________
wildfly-dev mailing list --wildfly-dev(a)lists.jboss.org
To unsubscribe send an email towildfly-dev-leave(a)lists.jboss.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s