Uploaded image for project: 'Jackrabbit Content Repository'
  1. Jackrabbit Content Repository
  2. JCR-4060

unintended export versions due to changed defaults in maven bundle plugin

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 2.12.5, 2.13.4
    • Fix Version/s: 2.13.6, 2.14, 2.12.7
    • Component/s: None
    • Labels:
      None

      Description

      It appears that the maven bundle plugin change for JCR-3937 has caused default export version numbers to be assigned where before we hadn't any.

      For instance, in jackrabbit-api, the package "o.a.j.api" has a package-info.java setting the version to 2.4, and this is what get's exported.

      However, o.a.j.api.query does not have a package-info, and now gets exported with a version number of 2.13.5, whereas previously it didn't get any version number.

      a) Does anybody know whether this change in behavior of the bundle plugin is documented anywhere?

      b) Do we need to fix something here, or are automatically assigned version numbers indeed ok? If we need to do something, what is the correct fix? Freeze the version numbers at the currently assigned version?

        Attachments

        1. ExportVersionChecker.jar
          2 kB
          Julian Reschke
        2. ExportVersionChecker.java
          2 kB
          Julian Reschke

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                reschke Julian Reschke
              • Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: