Re: [mojarra-dev] JSF TCK

[arjan tijms <arjan.tijms@xxxxxxxxx>]

Hi,

That's very good news regarding the TCK! Thx :)

Some of Mojarra's own tests have been run locally. There is already a ticket for running those via Jenkins, but we haven't succeeded in actually closing that issue yet (or even starting with it). See https://github.com/eclipse-ee4j/mojarra/issues/4520

Kind regards,

Arjan

On Sun, Dec 23, 2018 at 9:44 PM Edward Bratt <ed.bratt@xxxxxxxxxx> wrote:

Adding Mojarra Dev. list.

The latest TCK round-up was from a GlassFish build of Dec. 20.

There were no JSF TCK failures with this run. Presumably, this includes the latest, shared Eclipse Mojarra components. See this link for the test summary.

The project teams are responsible for running stand-alone product verification tests. So, someone from the Mojarra dev team would need to point us to that, or whatever substitutes for those results. Many projects just combine their components with a trial GlassFish build and run the TCK tests, based on a GlassFish build. I am not sure what Mojarra does, in this regard. I did not see anything obvious in the Eclipse Mojarra Jenkins tests.

Mojarra team is responsible for ensuring their components pass all required compatibility tests.

If you have specific concerns, don't hesitate to raise them.

-- Ed

On 12/22/2018 12:08 PM, dmitry.kornilov@xxxxxxxxxx wrote:

+Romain

 

From: arjan tijms <arjan.tijms@xxxxxxxxx>
Sent: Saturday, December 22, 2018 7:28 PM
To: Ed Bratt <ed.bratt@xxxxxxxxxx>; manfred riem <manfred.riem@xxxxxxxxxx>; Dmitry Kornilov <dmitry.kornilov@xxxxxxxxxx>
Cc: Bauke Scholtz gmail <balusc@xxxxxxxxx>
Subject: JSF TCK

 

Hi,

 

Just wandering, has the JSF TCK been run against Mojarra again (with a clean maven repo)?

 

Kind regards,

Arjan