jsr358
  1. jsr358
  2. JSR358-75

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

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Component/s: None
    • Labels:
      None

      Description

      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.

        Issue Links

          Activity

          pcurran created issue -
          pcurran made changes -
          Field Original Value New Value
          Link This issue is duplicated by JCPNEXT4-33 [ JCPNEXT4-33 ]
          pcurran made changes -
          Status Open [ 1 ] Closed [ 6 ]
          Resolution Fixed [ 1 ]

            People

            • Assignee:
              Unassigned
              Reporter:
              pcurran
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: