[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakartaee-platform-dev] [External] : Re: : Re: Pushing RCx or Mx to maven central
|
You are correct. Any API JAR can be used. Certification involves both
passing the TCK as well as implementation all the requirements contained
in the final normative objects.
As much as we wish the TCKs covered 100% of the required functionality,
they do not. We rely heavily on all implementations to do the right
thing and we generally don't look deeper than the TCK results.
Generally, that has worked well for the specification.
-- Ed
On 1/13/2022 10:37 AM, David Blevins wrote:
Some history here for everyone's benefit.
The short version is when it comes to certification, the API jar is the responsibility of the implementation.
In the early days everyone created their own API jars. The first open source API jars to hit Maven Central came from Apache Geronimo around 2004 under the ALv2 license and org.apache.geronimo.spec package. When GlassFish came round their API jars also hit Maven Central. I think that was around 2006, under CDDL and org.glassfish. Those eventually were renamed to the javax groupId, despite that some APIs are also implementations such as JavaMail and Activation and others like Apache did have compatible and equivalent implementations.
When we launched Jakarta and did our first releases, those same API jars still containing some implementations, were shipped to Maven Central under the jakarta.* groupId.
As time has gone on, fewer and fewer of us are creating our own unique API jars. It still remains true, however, that providing API classes is the responsibility of the implementation. The API jars we in the spec process are largely for convenience and to help verify we have a complete and implementable spec. They're useful for people to compile against and are equally helpful to vendors, but there is not a singular "official" API jar. Any API jar that passes the signature tests is equally official.
