webdav-interop
  1. webdav-interop
  2. WEBDAV_INTEROP-5

Wrong version range prevents using latest bug fixes

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: current
    • Fix Version/s: milestone 1
    • Component/s: www
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      5

      Description

      Currently the POM is using the POM range "1.1". This is problematic, since it
      prevents projects which are dependend on webdav-interop (like webdav-
      addressbook) to use a later (i. e. bug fixed) release (e. g. 1.1.1). As a
      result, those projects will possibly not run correctly, as they might be
      depdend on a particular fix (which is why they are using a range like
      [1.1.1,1.2) to indiciate that they need at least fix 1.1.1.

      To solve the problem, the version range should never be one static version
      like "1.1", but should always be a range of valid fixes, like "[1.1,1.2)" to
      indicate that any fix of 1.1 is suitable. In fact, webdav-interop is not
      dependend on exactly 1.1, it is guaranteed to work with any fix in that range
      (which is, why the webdav-jaxrs web site clearly says that exactly that range
      shall be used).

        Activity

        Hide
        mkarg added a comment -

        Created an attachment (id=2)
        Proposed solution to version range problem

        Show
        mkarg added a comment - Created an attachment (id=2) Proposed solution to version range problem
        Hide
        mkarg added a comment -

        Attached proposed solution.

        Show
        mkarg added a comment - Attached proposed solution.
        Hide
        mkarg added a comment -

        Daniel, can you please verify the fix and (if not rejected) commit it into SVN
        trunk?

        I am currently preparing webdav-jaxrs release 1.1.1 (collection of essential
        bug fixes), which I hope to publish on January 1st. Would be good if short
        after that, webdav-interop release 1.1.1 could get released, including this fix.

        Show
        mkarg added a comment - Daniel, can you please verify the fix and (if not rejected) commit it into SVN trunk? I am currently preparing webdav-jaxrs release 1.1.1 (collection of essential bug fixes), which I hope to publish on January 1st. Would be good if short after that, webdav-interop release 1.1.1 could get released, including this fix.
        Hide
        daniel_manzke added a comment -

        WAIT FOR RELEASE 1.2

        Show
        daniel_manzke added a comment - WAIT FOR RELEASE 1.2

          People

          • Assignee:
            daniel_manzke
            Reporter:
            mkarg
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: