Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-4731

use p2.mirror w/ comparator to verify plugin/feature versions are correctly incremented between builds/baselines

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Blocker
    • 4.1.2.Final
    • None
    • build

    Description

      This depends on having per-component builds and a buckminster/p2 aggregator to merge them into a single update site.

      See http://aniefer.blogspot.com/2009/08/versioning-p2-slides-from-eclipsecon.html for details on using p2.mirror w/ a comparator

      Attachments

        Issue Links

          is duplicated by

          Feature Request - Feature requests from customers and/or users JBIDE-2763 Add plugin versioning check

          • 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
          is related to

          Sub-task - The sub-task of the issue JBIDE-15160 support comparing bundle folders as well as bundle jars when comparing MD5 sums

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

          Sub-task - The sub-task of the issue JBIDE-15159 versionwatch should not report something red then yellow if nothing has changed (version not bumped)

          • 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

          Task - Represents a small unit of work that is not end-user facing. JBIDE-15114 Check if versions has been bumped for all modified components

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          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) JBIDE-15339 Create version/change auditor/reporting tool

          • 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
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-13478 create job to check IUs are being properly upversioned between releases

          • 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

              nickboldt Nick Boldt
              nickboldt Nick Boldt
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: