Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [websocket-dev] [tyrus-dev] Coordinating between Tyrus and WebSocket

I have run the web-socket TCK, using the Stand-alone TCK test tool with this week's GlassFish Weekly Build.

The results are here:

Full Log: https://ci.eclipse.org/jakartaee-tck/job/jakartaee-tck/job/master/1104/consoleFull

GlassFish build: https://download.eclipse.org/ee4j/glassfish/weekly/glassfish-6.0.0-SNAPSHOT-2020-10-04.zip

The weekly build details are here.

Using the current "Promoted" Web Socket TCK: https://download.eclipse.org/ee4j/jakartaee-tck/jakartaee9-eftl/promoted/jakarta-websocket-tck-2.0.0.zip

SHA 256: 3afbe37c5de2b0bc487b06bda9e82900863a797dcd21a853f63fc46b5592fc9a

All looks good to me.

Could someone verify that the JAR in this build of GlassFish does contain the module names as we expect them?

Jan, if you are satisfied, please file a Compatibility Certification Request for Tyrus? You may use Tyrus web-pages., or the GlassFish web-pages. I have submitted a PR for GlassFish TCK summary, here. You may use this, or a summary created in the Tyrus project.

Thank you,

-- Ed

On 10/2/2020 3:51 AM, Joakim Erdfelt wrote:

WebSocket API was restaged at version 2.0.0 and is now available at the stage repository at https://jakarta.oss.sonatype.org/content/repositories/jakartawebsocket-1010/

Example: https://jakarta.oss.sonatype.org/content/repositories/jakartawebsocket-1010/jakarta/websocket/jakarta.websocket-client-api/2.0.0/


- Joakim


On Tue, Sep 29, 2020 at 11:48 AM Ed Bratt <ed.bratt@xxxxxxxxxx> wrote:

For the WebSocket API team: Is there any plan to re-stage the release, incorporating the Module Name changes that were merged a few days ago (PR 357)? I think we would like to see that included in Jakarta EE 9.

Please let me know -- this is what, I believe requires the coordination/staging that I outlined below.

Thanks,

-- Ed

On 9/29/2020 3:35 AM, Jan Supol wrote:
Hi Ed,

We plan to update Tyrus this week. For the TCK, Tyrus grabs whatever WebSocket API is in GF, and hence on the TCK classpath. Do you register any issue with the TCK run after the WebSocket Final API has been integrated to GF?

Thanks,

Jan

On 28.09.2020 17:21, Ed Bratt wrote:
Hi,

Do we have a mechanism for keeping Eclipse Tyrus and the latest Web Socket artifacts in Sync? I ask because we will need to be sure that Tyrus picks up the final JAR bundles from WebSocket, once they are ready -- after that, Tyrus will need to be updated in Eclipse GlassFish as well.

Once these things are accomplished, we can finalize the TCK results summary for GlassFish.

Are issues in place for this already? Perhaps they should be created?

-- Ed

_______________________________________________
tyrus-dev mailing list
tyrus-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/tyrus-dev__;!!GqivPVa7Brio!M27LcYGBvI5Ijc33yteVQMYmCJ7TOZ9PK6DfeJbn8uH6U_CWmWiKI7pDDggKE8nF$

_______________________________________________
websocket-dev mailing list
websocket-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/websocket-dev

_______________________________________________
websocket-dev mailing list
websocket-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/websocket-dev__;!!GqivPVa7Brio!Lc366ASKOYPq-r22a4bzQEJe2oCtlti8ErONBAQX10Ie2Znormn01gSr9oh-YRU$

Back to the top