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

How to automate process of bumping version for changed modules/submodules for every release

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Optional
    • 4.5.1.AM1
    • 4.1.0.Beta1
    • build

    Description

      The versions of plugins are constantly discovered to not be uptodated when they should and things like Usage and others where it is critical are not getting bumped.

      We need two things:
      A) detect when versions are not bumped properly - we got parts of this in various places, but they are not run nor documented regularly (having a green build verifying versions are not conflicting would be a Good Thing)

      B) document/automate a process which every affected lead can follow to make this happen and if not See #A

      Attachments

        Issue Links

          is related to

          Feature Request - Feature requests from customers and/or users JBIDE-13655 Usage needs to bump versions for each release currently - how to fix or automate ?

          • 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

          Feature Request - Feature requests from customers and/or users JBIDE-14643 Usage needs to bump versions for each release currently

          • 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

          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-19056 A Mojo to validate a version (compared to baseline)

          • 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

          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

          Activity

            People

              nivologd@gmail.com Denis Golovin (Inactive)
              nivologd@gmail.com Denis Golovin (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: