Re: [jakartaee-platform-dev] Unreleased former Java SE specifications

["Kevin Sutter" <sutter@xxxxxxxxxx>]

>  At
this stage maybe a good way to get them across the finish line would be
to review them and say "these look great, we would vote +1 if the
API jars were published and the vote proposed."

Thanks, David.  I had temporarily
added the "hold" label on these Spec PRs just due to these discussions
on the Platform project.  Based on these discussions, I think it would
be best to just move these forward to the Jakarta/EE4J projects per the
original plan.  That is not a statement that we are "jakarta-izing"
them or including them in the Platform.  It just allows us to do the
next steps, if deemed appropriate.

We should probably queue this discussion
for the Specification Committee call tomorrow to let the team know that
these votes are on the horizon.

Also, to avoid this constant respin of
the API jar files, it was proposed at a recent Platform call (and is part
of our Release Plan) to promote "RC" versions of the API jar
files and actually push them to Maven.  For example, push Jakarta
Activation 1.2-RC1 API to Maven.  This allows a preliminary version
to be accessible for examination and testing.  And, once we are ready
for the vote, then the final 1.2 version could be pushed to the staging
repo.  Once the vote passes, then the 1.2 artifacts could be released.


---------------------------------------------------
Kevin Sutter 
STSM, MicroProfile and Jakarta EE architect
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter



From:
       David
Blevins <dblevins@xxxxxxxxxxxxx>
To:
       jakartaee-platform
developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Date:
       12/03/2019
12:59
Subject:
       [EXTERNAL]
[jakartaee-platform-dev] Unreleased former Java SE specifications
Sent
by:        jakartaee-platform-dev-bounces@xxxxxxxxxxx

---

Here are the Jakarta-owned specifications
that were removed in Java SE 11.

 - https://github.com/jakartaee/specifications/pulls?q=is%3Apr+is%3Aopen+label%3Ajavase

Until they are released under the JESP,
the only official TCK binaries for them are the Oracle licensed TCK binaries.

I might wrong on this next sentence,
but my understanding is getting these across the finish line would be a
requirement to allowing a Jakarta EE 9 implementation to legally ship JAXB,
JAX-WS, Activation, etc without a preexisting licensing agreement.

The work has been done on preparing these
TCK binaries and getting GlassFish 5.1 to pass, however the API jars keep
expiring before we get the attention needed to get votes up.  Lukas
in particular has been beyond a good sport, rolling the API jars several
times.

At this stage maybe a good way to get
them across the finish line would be to review them and say "these
look great, we would vote +1 if the API jars were published and the vote
proposed."


-- 
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
310-633-3852
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev