Uploaded image for project: 'Weld'
  1. Weld
  2. WELD-1712

Package version should reflect API changes

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 2.1.2.Final, 2.2.4.Final
    • Fix Version/s: 2.2.5.Final
    • Component/s: OSGi support
    • Labels:
      None

      Description

      All versions of weld-osgi-bundle I looked at export their own packages with version 1.0.0, regardless of the Weld release.

      This would only make sense if the Weld public API were unchanged since Weld 1.x. Looking at the class lists, it is easy to see some differences, so the API did change.

      The easiest fix would be to set the package version to the Weld release version.

      Semantic versioning would also be an option if it's possible to decide whether or not an API change was backward compatible.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jharting Jozef Hartinger
              Reporter:
              hwellmann.de Harald Wellmann (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: