JSR358-75: Although there is no TCK for process-change JSRs we ought to "test" whether we successfully implement the changes we specify

jcp-org / jsr358

0 stars 0 forks source link

JSR358-75: Although there is no TCK for process-change JSRs we ought to "test" whether we successfully implement the changes we specify #52

Closed apastsya closed 7 years ago

apastsya commented 10 years ago

Jira issue originally created by user pcurran:

Appendix A of the Process Document makes it clear that for process-change JSRs there is not RI or TCK.

Another way to look at this is to say that the new version of the Process as implemented is the RI. From this perspective we really ought to specify a verification process to check whether what we implement actually conforms to what we specified in the JSR.

apastsya commented 10 years ago

is duplicated by JCPNEXT4-33: Although there is no TCK for process-change JSRs we ought to "test" whether we successfully implement the changes we specify

apastsya commented 9 years ago

Comment created by pcurran:

This is fixed in the version of the Process Document being developed through JSR 364.

apastsya commented 9 years ago

Issue was closed with resolution "Fixed"