uel
  1. uel
  2. UEL-32

Missing el api jar for version 3.0

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Works as designed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Previous versions of the el spec provided both an -api and an -impl jar. There seems to now be only a single jar that contains both api and impl available from the maven repository:

      http://repo1.maven.org/maven2/org/glassfish/javax.el/

      The api should be split out of the impl jar.

        Activity

        Hide
        janbartel added a comment -

        Let me clarify that. There is in fact v3.0 el-api jar here: http://repo1.maven.org/maven2/javax/el/javax.el-api/3.0-b08/
        It is at version level 3.0-b08.

        The latest v3.0 el-impl jar is here: http://repo1.maven.org/maven2/org/glassfish/javax.el/3.0-b07/
        It is at version level 3.0-b07.

        There are 2 problems here:

        1. the impl jar is 1 version behind the api jar
        2. the impl jar contains both the api classes and impl classes

        thanks
        Jan

        Show
        janbartel added a comment - Let me clarify that. There is in fact v3.0 el-api jar here: http://repo1.maven.org/maven2/javax/el/javax.el-api/3.0-b08/ It is at version level 3.0-b08. The latest v3.0 el-impl jar is here: http://repo1.maven.org/maven2/org/glassfish/javax.el/3.0-b07/ It is at version level 3.0-b07. There are 2 problems here: 1. the impl jar is 1 version behind the api jar 2. the impl jar contains both the api classes and impl classes thanks Jan
        Hide
        kchung added a comment -

        The artifacts for EL 3.0 are following the guide lines specified in https://wikis.oracle.com/display/GlassFish/Maven+Versioning+Rules. All Java EE 7 modules (e.g. JSF) are following the same rules regarding naming, versioning, and packaging.

        Regarding your specific complaints,

        1. The api and impl can have independent minor versions to allow independent releases.
        2. The impl now also includes the api, as allowed and encouraged by the rules above. This is easier for the user and avoid the matching-implementation-with-the-correct-api problem.

        Show
        kchung added a comment - The artifacts for EL 3.0 are following the guide lines specified in https://wikis.oracle.com/display/GlassFish/Maven+Versioning+Rules . All Java EE 7 modules (e.g. JSF) are following the same rules regarding naming, versioning, and packaging. Regarding your specific complaints, 1. The api and impl can have independent minor versions to allow independent releases. 2. The impl now also includes the api, as allowed and encouraged by the rules above. This is easier for the user and avoid the matching-implementation-with-the-correct-api problem.

          People

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

            Dates

            • Created:
              Updated:
              Resolved: