Re: [jakartaee-tck-dev] [External] : Re: Is TCK compliance required by d

[Scott Marlow <smarlow@xxxxxxxxxx>]

On 12/8/21 2:06 PM, Lukas Jungmann wrote:

> On
>       12/8/21 7:49 PM, Ed Bratt wrote:
>       
> > Java EE's stated requirement was that a
> >         compatible product must be compatible in all configurations.
> >         This requirement was written but enforcement of this (and other
> >         requirements) was left to the implementation organization or
> >         team.
> >         
> >         
> >         I'm not aware that the written form of these requirements has
> >         changed in the migration to Jakarta EE.
> >         
> >         
> >         What specific problems are you encountering? Perhaps the
> >         specification should be updated to allow for the specific
> >         behavior issues and/or complexities you are finding.
> >         
> >       
>       
>       Basically, can a compatible implementation say "..there are
>       compatibility configurations that you must set in order for [a
>       product] to behave fully spec compliant."?
>       
>

I see no problem with saying that configuration changes have to be made in order to run the TCK tests.

    Scott
>       
>       thanks,
>       
>       --lukas
>       
>       
> >         
> >         -- Ed
> >         
> >         
> >         On 12/8/2021 10:16 AM, Lukas Jungmann wrote:
> >         
> > > On 12/8/21 6:04 PM, Scott Stark wrote:
> > >           
> > > > I believe this has been relaxed to
> > > >             effectively some configuration as there is no discussion of
> > > >             this in the TCK process:
> > > >             
> > > > https://urldefense.com/v3/__https://jakarta.ee/committees/specification/tckprocess/__;!!ACWV5N9M2RV99hQ!cBpaoUEKi0lORbkHJRPhjoSLZWNafDHOju_YmVMYBnkag3ZIcFzbjBn4t517x9I$
> > > > <https://urldefense.com/v3/__https://jakarta.ee/committees/specification/tckprocess/__;!!ACWV5N9M2RV99hQ!b26NLrg_lDo2FbedfEg1sB7MQVUtbO7oRp61i5676CjynH9BiQhyfWM_EztqHS42Q2M$>
> > > >             
> > > >             
> > > >             If the platform user guide says otherwise, I think that
> > > >             should be changed.
> > > >             
> > > >           
> > >           
> > >           there are also standalone TCKs. Do you think it would make
> > >           sense to make the "some configuration" explicit in the TCK
> > >           process or is it expected that non-platform TCKs can define
> > >           this differently?
> > >           
> > >           
> > >           thanks,
> > >           
> > >           --lukas
> > >           
> > >           
> > > >             
> > > >             On Dec 8, 2021 at 10:36:00 AM, Lukas Jungmann
> > > >             <lukas.jungmann@xxxxxxxxxx
> > > >             <mailto:lukas.jungmann@xxxxxxxxxx>> wrote:
> > > >             
> > > > > Hi,
> > > > >               
> > > > >               
> > > > >                  under Java EE, there is/was the rule that to claim a
> > > > >               compatibility,
> > > > >               
> > > > >               a product must pass TCKs in product's default
> > > > >               configuration. Is there
> > > > >               
> > > > >               the same requirement to claim compatibility under Jakarta
> > > > >               EE or was it
> > > > >               
> > > > >               relaxed to say "a product must pass TCK in _some_
> > > > >               configuration"? The
> > > > >               
> > > > >               question is about default vs some configuration of a
> > > > >               product to pass TCK
> > > > >               
> > > > >               tests under Jakarta EE.
> > > > >               
> > > > >               
> > > > >               thanks,
> > > > >               
> > > > >               --lukas
> > > > >               
> > > > >               _______________________________________________
> > > > >               
> > > > >               jakartaee-tck-dev mailing list
> > > > >               
> > > > >               jakartaee-tck-dev@xxxxxxxxxxx
> > > > >               <mailto:jakartaee-tck-dev@xxxxxxxxxxx>
> > > > >               
> > > > >               To unsubscribe from this list, visit
> > > > > https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev__;!!ACWV5N9M2RV99hQ!cBpaoUEKi0lORbkHJRPhjoSLZWNafDHOju_YmVMYBnkag3ZIcFzbjBn4SL4CY8A$
> > > > > <https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev__;!!ACWV5N9M2RV99hQ!b26NLrg_lDo2FbedfEg1sB7MQVUtbO7oRp61i5676CjynH9BiQhyfWM_EztqhMYqrdQ$>
> > > > >               
> > > > >             
> > > >             
> > > >             _______________________________________________
> > > >             
> > > >             jakartaee-tck-dev mailing list
> > > >             
> > > >             jakartaee-tck-dev@xxxxxxxxxxx
> > > >             
> > > >             To unsubscribe from this list, visit
> > > > https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev__;!!ACWV5N9M2RV99hQ!b26NLrg_lDo2FbedfEg1sB7MQVUtbO7oRp61i5676CjynH9BiQhyfWM_EztqhMYqrdQ$
> > > >             
> > > >             
> > > >           
> > >           
> > >           _______________________________________________
> > >           
> > >           jakartaee-tck-dev mailing list
> > >           
> > >           jakartaee-tck-dev@xxxxxxxxxxx
> > >           
> > >           To unsubscribe from this list, visit
> > > https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev__;!!ACWV5N9M2RV99hQ!cBpaoUEKi0lORbkHJRPhjoSLZWNafDHOju_YmVMYBnkag3ZIcFzbjBn4SL4CY8A$
> > >         
> >         
> >         
> >       
>       
>       _______________________________________________
>       
>       jakartaee-tck-dev mailing list
>       
>       jakartaee-tck-dev@xxxxxxxxxxx
>       
>       To unsubscribe from this list, visit
>       https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
>       
>