| Re: [servlet-dev] Question about CI for Servlet |
Arjan
Can you confirm -- are the Servlet Implementation JARs in the GlassFish repository, or in the Servlet repository? If the latter, perhaps, we can correctly identify the release from the Servlet repo. as the compatible implementation.
Would that be a fair statement?
-- Ed
Not deleting and tagging is probably easiest for now. I'll check with the GlassFish team to see if they can make arrangements. Probably they should be called something other than Snapshot releases too.
Thank you Arjan
-- Ed
On 9/30/2020 10:02 AM, arjan tijms wrote:
Hi,
In the case of Servlet, the compatible implementation resides embedded within GlassFish (it's mostly in https://github.com/eclipse-ee4j/glassfish/tree/master/appserver/web), so GlassFish itself is the compatible implementation.
I'd like to argue for extra RC versions to be made available, perhaps for every wave, or on a monthly basis.
For now we might want to simply not delete the weekly folder where the weekly builds are copied to?
Kind regards,Arjan
On Wed, Sep 30, 2020 at 6:49 PM Ed Bratt <ed.bratt@xxxxxxxxxx> wrote:
Hi,
In the Jakarta EE Spec. committee, a question has been raised about the
compatible implementation for Servlet. The Spec. ballot referenced
Eclipse GlassFish Snapshot release -- is that the test vehicle, or the
compatible implementation? If the compatible implementation comes from
Servlet project and is pulled into Eclipse GlassFish, perhaps we simply
mistakenly referenced GlassFish as the compatible implementation -- and
Eclipse GlassFish snapshot was just the vehicle to confirm that the
released Servlet implementation passed.
Specification: https://jakarta.ee/specifications/servlet/5.0/
CCR:
https://github.com/eclipse-ee4j/servlet-api/issues/339#issuecomment-701440147
TCK Results:
https://eclipse-ee4j.github.io/glassfish/certifications/jakarta-servlet/5.0/TCK-Results.html
If the Compatible implementation is Eclipse GlassFish, we will want to
use a released version that won't be overwritten. Apparently, Snapshot
is viewed as an over-writable release. (I wasn't aware of this nuance.)
If we want to use Eclipse GlassFish for this, we will want the release
to be tagged and archived for future reference. In this case, we should
coordinate these requirements with the GlassFish team as well.
What's the case for this project?
-- Ed
PS if it's any consolation, I don't think that Servlet is necessarily
unique in this issue. Separately, the Specification Committee will be
working to improve their documentation of requirements for this, for
future releases.
_______________________________________________
servlet-dev mailing list
servlet-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/servlet-dev
_______________________________________________ servlet-dev mailing list servlet-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/servlet-dev__;!!GqivPVa7Brio!IZZ6X0KfKRIYz9AiqCEyLkZw_HbUTnjL1DUxp46J0I-ZDeI2JjK_fQHJQVe9WOk$