Yep, the "official" requirement for certification is the in-container tests, but we should resolve the failures under both runs, as there isn't a perfect intersection of failures.
-Donald On 5/19/10 5:00 PM, Carlos Vara wrote: > Wow, I truly expected to have more failures in incontainer tests, > specially taking into account that a few more tests are run, really > nice to see the opposite. > > Thanks for completing the pom Donald, seeing the good results gives > energy to continue! > > On Wed, May 19, 2010 at 9:08 PM, Donald Woods <[email protected]> wrote: >> r946365 included a bval-tck/pom.xml update to include missing >> dependencies for incontainer runs. Using JBoss 5.1.0.GA for jdk6, we're >> down to 15 failures for incontainer runs and 34 failures for stand-alone >> runs. >> >> mvn -Ptck,incontainer -Djboss.home=<path_to_jboss-5.1.0.GA> >> >> >> -Donald >> >> >> On 4/1/10 9:46 PM, Carlos Vara (JIRA) wrote: >>> Maven project to launch TCK suite >>> --------------------------------- >>> >>> Key: BVAL-16 >>> URL: https://issues.apache.org/jira/browse/BVAL-16 >>> Project: BeanValidation >>> Issue Type: Improvement >>> Components: tck >>> Affects Versions: 0.1-incubating >>> Reporter: Carlos Vara >>> Priority: Minor >>> Attachments: bval-tck-runner.tar.gz >>> >>> I didn't find code to run the TCK against the current code. As I wanted to >>> check to which degree the project complies with the standard I created an >>> additional maven project to automatically run the TCK suite. I attach it in >>> case you don't have it internally. >>> >>> I used hibernate-validator-tck-runner as template, just in case it matters >>> for licensing issues. >>> >> >
