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

Update the JAPICMP settings so that we only detect changes that break API compatibility

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • 1.2.4.Final, 1.3.0.Final
    • None
    • Build
    • None

    Description

      Currently, the JAPICMP settings will result in a build failure if new public API has been added. As we will be tagging .Final releases more regularly, we need to be able to allow new public API into a patch release so we should only be detecting changes that break API compatibility not changes that add new public API.

      Attachments

        Issue Links

          relates to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBEAP-14225 (7.1.z) Verify public API signatures during Elytron 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.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: