Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec.committee] Possible issue with Servlet spec PR
Hi,

>Bottom line: Fix the revised JAR -- update the PR if necessary -- no changes needed for the compatibility certification request -- should be good. The Ballot can start once everything has been checked out and confirmed.

With the great help of Scott we have fixed and published the issue right away:


Newly staged jar

Now trying to figure out why the signature tests where excluded from the default run.

Kind regards,
Arjan 






On Tue, Aug 20, 2019 at 9:07 PM Ed Bratt <ed.bratt@xxxxxxxxxx> wrote:

I can't see any evidence that Servlet Ballot has started.

The publication of the Jakarta Branded API (and JavaDocs) can be independent from the compatible implementation. The branded API must be quality tested -- and you have found that the signature tests fail. So you need to fix that and push a fixed, branded API JAR.

The Compatible Implementation only needs to pass the TCK -- it does not require revised JavaDocs. So, the compatibility certification could be approved as it currently stands.

GlassFish 5.1, since it was released prior to the existence of Jakarta EE 8, cannot be used as a validation of the Jakarta EE 8 specifications nor any of the branded/updated Jakarta JARs. It can be declared a compatible implementation if it passes all required tests. I believe that it does. Test builds, built with the revised JARs, which are proposed for release can be used to validate the revised JARs, the component JARs are released, but the Platform isn't.

Near as I can see - the compatibility request ought to remain valid for consideration -- the revised JAR (and associated JavaDocs) needs to be fixed and republished. If you need to change the version number, I don't think that is a catastrophic change, but please make sure that the folks who might be tracking these version IDs are aware that it's changed.

Bottom line: Fix the revised JAR -- update the PR if necessary -- no changes needed for the compatibility certification request -- should be good. The Ballot can start once everything has been checked out and confirmed.

-- Ed

On 8/20/2019 10:46 AM, Scott Stark wrote:
That is the only thing I can see to do.

On Aug 20, 2019, at 10:43 AM, Kevin Sutter <sutter@xxxxxxxxxx> wrote:

So, we need to kill the current Servlet 4.0 ballot, get it corrected, and re-submit?


---------------------------------------------------
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



_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee

Back to the top