[
https://issues.apache.org/jira/browse/BVAL-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12854127#action_12854127
]
Donald Woods commented on BVAL-16:
----------------------------------
Good point. I was erring on the side of caution, as the TCK materials I have
are covered under the NDA and it'll be hard to tell who is using a copy
acquired from the JBoss repo under ASL 2.0 vs. the ASF acquired files....
Guess we can setup two TCK profiles - one that uses the JBoss files and another
that uses the NDA covered files.
Then, in publicly discussing problems, we'll just have to make sure we're using
the JBoss sourced files....
Sounds like a good topic to add to the wiki.
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
