|Re: [jakartaee-platform-dev] Releasing api jars to central|
Of course on the invididual spec level committers who are independent or work for smaller companies than Oracle, IBM, Payara, etc. are very welcome to help, but it is mostly Arjan (in almost a dozen of them) or Markus (only REST from what I saw), myself (I mentored 3 in the Spec Committee and help those where I am a project member as much as I can) and maybe one or two others, but for all the other specs it is up to employees of a few larger vendors and it is usually the same people who are responsible for 3-6 Jakarta EE specs, at least one or more MP specs and some probably have to support either their Commercial products or customers on top.
That’s because some have too many "hats" and things they juggle in parallel.
E.g. Steve and Payara just submitted yet another version of their Server for Jakarta EE compatibility (still 8 of course) while others especially TomEE have not even done so ever since Java EE 6 !!!
Most contributors try to put up a redundant MicroProfile WG with its own infrastructure and administrative burden like meetings and calls instead of true synergy in one ecosystem, so there are multiple votes for each of them which causes them to lag behind in many cases both in Jakarta EE and MP. Unless many of them hire twice as many people that is unlikely to change.
Gesendet von Mail für Windows 10
Werner, yes, I mean the Jakarta EE platform. And no, it is definitively NOT done like that. There are some JARs currently NOT uploaded to Maven central while the ballot has successfully passed already (I checked that yesterday). And, some projects went into ballot with MRs/RCs definitively. If that wouldn't be the case, Steve never would have had a need to ask and I never have had to explain.
With "Jakarta EE itself" I assume you mean the platforms like Full or Web Platform?
What you mentioned is done just like that at the moment. ;-)
All the individual specs were voted on before the Platform ballots took place.
Some were done relatively "Long before" others only a few weeks ago, but all happened before the platforms.
The standalone specs are also separate and only referenced from the platform specs in ways like
"The Jakarta Annotations specification can be found at https://jakarta.ee/specifications/annotations . "
I'd like to extend Ivar's answer by one point: Specs can publish many releases within the lifetime of one Jakarta EE release, hence their pushing is always unrelated of Jakarta EE and typically should be done *long before* Jakarta EE is iteself starting its ballot. In fact, what people "out there" expect is that the ballot for Jakarta EE is basing on already published specs, not basing on Milestones or Candidates. Looking on Jakarta EE from that point makes it clear that EE 8 and EE 9 enforced unneccessary and unwanted waiting, and we should never again without anything that successfully passed a ballot. These are not chapters of a book, these are standalone documents.
Thanks I will get the checklist steps done now then
That is part of the competition steps for the specification project team after their ballot is passed. Should be done for each component specification as soon as possible after the ballot completes.
On Wed, Nov 18, 2020 at 6:54 PM Steve Millidge (Payara) <steve.millidge@xxxxxxxxxxx> wrote:
Jakarta EE Developer Advocate | Eclipse Foundation, Inc.
Eclipse Foundation - Community. Code. Collaboration.
Back to the top