Uploaded image for project: 'WildFly Elytron'
  1. WildFly Elytron
  2. ELY-1572

japicmp force source compatibility, but only binary compatibility is required

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 1.4.0.Final
    • 1.3.0.Final
    • Build
    • None

    Description

      As part of ELY-1523 japicmp was configured to force binary and source compatibility.
      By last discussion, only binary compatibility is required.

      Honza Kalina jaspicmp reports it as source incompatibility, not as binary incompatibility - so it maybe it is false positive, as I would say it should be source-compatible...
      Darran Lofthouse Binary is the only one we are really interested in, i.e. will an update to a later version of Elytron break something. Most of our backwards compatibility strategy is more about breaking things and upsetting people

      Japicmp currently reports adding default method into interface as source incompatible change (see https://github.com/siom79/japicmp/issues/201) -> blocks adding IV into MaskedPassword in ELY-867

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. ELY-1587 X500 principal [CN=client] was not decoded - no values of attribute [2.5.4.3]

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. ELY-867 Masked password support cryptography usage

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is related to

          Bug - A problem that impairs or prevents the functions of the product. ELY-1595 Reenable source compatibility check during build

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          links to

          Web Link japicmp: New methods in interfaces...

          Activity

            People

              jkalina@redhat.com Jan Kalina (Inactive)
              jkalina@redhat.com Jan Kalina (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: