|Re: [jakartaee-tck-dev] Question about running Faces old TCK tests for EE 10 TCK testing...|
I have my user hat on now for this email. We are trying to get the Faces old-tck tests running/passing with WildFly. Previously we ran those tests as part of the Platform TCK which had the `config.vi` task defined in the $TS_HOME/bin/build.xml but I do not see the same task defined in the faces-tck-4.0.1/tck/old-tck/source/release/JSF_BUILD/latest/faces-tck/bin/build.xml file as I would expect and as a result I see failure .
Are others seeing the  failure?
Thanks Alwin for explaining to me that some of the Standalone TCKs generated from the Platform TCK use the `config.vi` task and some do not. Personally, I would be in favor of using the `config.vi` task in all of the (Platform TCK generated) Standalone TCKs if possible.
It may also be nice to consider allowing the Platform TCK
`ts.jte` configuration files to be used with the various
Standalone TCKs (as much as possible by supporting the `javaee`
base property prefix).
Both of these changes could ease the pain for an EE
implementation to transition from running the Platform TCK Faces
tests to running the Standalone Faces 4.0 (old) TCK. The same
could be true for other Standalone TCKs.
The Security TCK does include the `config.vi` task  but that is missing from the Faces TCK . I think we should update  to include `config.vi` if that helps. Does that sound like something we should create a TCK challenge to request? I haven't tried making this change locally yet.
 BUILD FAILED
Target "config.vi" does not exist in the project "JSF top level".
Back to the top