jsr348
  1. jsr348
  2. JSR348-118

profiles can be based on latest or next platform version

    Details

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

      Description

      In 2.1.3, line 392, change "latest version" to "most recent Release version or
      a newer version under development via an active UJSR".

        Activity

        Hide
        pcurran added a comment -

        This is pre-existing language (which I don't really understand) so I'm reluctant to make changes. The substitution you suggest doesn't result in anything that makes sense to me.

        Please suggest the complete replacement text that you'd prefer and I'll make the change.

        Show
        pcurran added a comment - This is pre-existing language (which I don't really understand) so I'm reluctant to make changes. The substitution you suggest doesn't result in anything that makes sense to me. Please suggest the complete replacement text that you'd prefer and I'll make the change.
        Hide
        Bill Shannon added a comment -

        That was the complete replacement text.

        If Java EE 6 has been released, and I'm developing Java EE 7, and I want
        to create a new Profile based on Java EE, which version is the "latest"?

        If "6", that means I'm not allowed to create a new Profile to be released
        coincident with or later than EE 7.

        If "7", and (e.g.) EE 7 isn't due to be released for a few years, that means
        I can't create a new Profile based on EE 6 to be released this year, before
        EE 7.

        I think both cases should be allowed, thus the suggested change.

        (You can imagine other failure cases, depending on the speed of the independent
        JSRs. I don't propose fixing those here.)

        Show
        Bill Shannon added a comment - That was the complete replacement text. If Java EE 6 has been released, and I'm developing Java EE 7, and I want to create a new Profile based on Java EE, which version is the "latest"? If "6", that means I'm not allowed to create a new Profile to be released coincident with or later than EE 7. If "7", and (e.g.) EE 7 isn't due to be released for a few years, that means I can't create a new Profile based on EE 6 to be released this year, before EE 7. I think both cases should be allowed, thus the suggested change. (You can imagine other failure cases, depending on the speed of the independent JSRs. I don't propose fixing those here.)
        Hide
        pcurran added a comment -

        Your suggestion would change:

        "all UJSRs to define new Profile Specifications or revise existing Profile Specifications must reference the latest version of the Platform Edition
        Specification they are based upon."

        to:

        "all UJSRs to define new Profile Specifications or revise existing Profile Specifications must reference the most recent Release version or a newer version under development via an active UJSR of the Platform Edition Specification they are based upon."

        which is gramatically incorrect (or at least confusing).

        Does this express what you mean?

        "all UJSRs to define new Profile Specifications or revise existing Profile Specifications must reference either the most recent Release version of the Platform Edition Specification they are based upon or a newer version of that Specification that is under development via an active UJSR."

        Show
        pcurran added a comment - Your suggestion would change: "all UJSRs to define new Profile Specifications or revise existing Profile Specifications must reference the latest version of the Platform Edition Specification they are based upon." to: "all UJSRs to define new Profile Specifications or revise existing Profile Specifications must reference the most recent Release version or a newer version under development via an active UJSR of the Platform Edition Specification they are based upon." which is gramatically incorrect (or at least confusing). Does this express what you mean? "all UJSRs to define new Profile Specifications or revise existing Profile Specifications must reference either the most recent Release version of the Platform Edition Specification they are based upon or a newer version of that Specification that is under development via an active UJSR."
        Hide
        Bill Shannon added a comment -

        What I intended (with parentheses added to make the grouping clearer):

        all UJSRs to (define new Profile Specifications) or (revise existing Profile
        Specifications) must reference ( ( (the most recent Release version) or (a newer
        version under development via an active UJSR) ) of (the Platform Edition Specification
        they are based upon) )

        Your alternate version is fine too.

        Show
        Bill Shannon added a comment - What I intended (with parentheses added to make the grouping clearer): all UJSRs to (define new Profile Specifications) or (revise existing Profile Specifications) must reference ( ( (the most recent Release version) or (a newer version under development via an active UJSR) ) of (the Platform Edition Specification they are based upon) ) Your alternate version is fine too.
        Hide
        pcurran added a comment -

        I went with my proposed wording, since Bill's had too many parentheses

        Now closed.

        Show
        pcurran added a comment - I went with my proposed wording, since Bill's had too many parentheses Now closed.

          People

          • Assignee:
            pcurran
            Reporter:
            Bill Shannon
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: