[jbosstools-issues] [JBoss JIRA] (JBIDE-14642) How to automate process of bumping version for changed modules/submodules for every release

[Nick Boldt (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-14642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt closed JBIDE-14642.
------------------------------
    Fix Version/s: 4.5.1.AM1
                       (was: 4.5.x)
       Resolution: Done


We've been using baseline checks for a couple years now, and they DO catch accidents where people forget to upversion.

So since there's been no movement here on creating a "build that does version validation" beyond what we have with versionwatch [1], I'm going to close this.

[1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio/view/devstudio_master/job/devstudio.versionwatch_master/

> How to automate process of bumping version for changed modules/submodules for every release
> -------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-14642
>                 URL: https://issues.jboss.org/browse/JBIDE-14642
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: build
>    Affects Versions: 4.1.0.Beta1
>            Reporter: Denis Golovin
>            Assignee: Denis Golovin
>            Priority: Optional
>              Labels: versioning
>             Fix For: 4.5.1.AM1
>
>
> 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



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)