Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-tck-dev] [External] : Jakarta Authentication TCK 3.0.1 staged 3.0.1-SNAPSHOT

I downloaded and searched the contents for `3.0.1-SNAPSHOT`and do see the snapshot reference in authentication-tck-3.0.1/tck/old-tck/build/pom.xml:


       <relativePath />


   <name>Old Jakarta Authentication TCK - build</name>

Is the idea that users are building the org.eclipse.ee4j.tck.authentication:old-authentication-tck:3.0.1-SNAPSHOT? 

On 7/6/22 6:42 AM, arjan tijms wrote:

On Wed, Jul 6, 2022 at 8:25 AM Alwin Joseph <alwin.joseph@xxxxxxxxxx> wrote:

Hi Arjan,


  1. I see the old-tck is not integrated with the main pom as a module to be executed from authentication-tck-3.0.1/tck. Is this expected? Should we be running the old tck tests separately from authentication-tck-3.0.1/tck/old-tck.

That's strange, they should run by default via the profile:


  1. I was trying to run the old tck tests from authentication-tck-3.0.1/tck/old-tck, using “mvn clean install -Pstaging,glassfish-ci-managed,platform -Dglassfish.version=7.0.0-M6”. I get pom.xml not found, possibly due to version mismatch between 3.0.1-SNAPSHOT and 3.0.1.

Does that also happen with the staged version, or only when running from a checkout of the repository?

Kind regards,
Arjan Tijms


Thanks & Regards,
Alwin Joseph


From: arjan tijms <arjan.tijms@xxxxxxxxx>
Date: Wednesday, 6 July 2022 at 1:32 AM
To: jaspic developer discussions <jaspic-dev@xxxxxxxxxxx>, jakartaee-tck developer discussions <jakartaee-tck-dev@xxxxxxxxxxx>
Cc: Gurunandan Rao <gurunandan.rao@xxxxxxxxxx>, Alwin Joseph <alwin.joseph@xxxxxxxxxx>, Darran Lofthouse <darran.lofthouse@xxxxxxxxx>
Subject: [External] : Jakarta Authentication TCK 3.0.1 staged



I just staged the service release of the Jakarta Authentication TCK here:


The major thing fixed in the service release is merging the two bundles from the 3.0.0 release into one. A smaller fix is printing the result summary directly in the log of a maven build. Previously the result summary was dependent on parsing the junit xml based file.


If the TCK bundle is found to be correct, we can initiate its promotion.


I just tested it on GlassFish 7.0 M6, where it passes.


Kind regards,

Arjan Tijms

jakartaee-tck-dev mailing list
To unsubscribe from this list, visit

Back to the top