[jbosstools-issues] [JBoss JIRA] (JBIDE-14642) How to automate process of bumping version for changed modules/submodules for every release
[
https://issues.jboss.org/browse/JBIDE-14642?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-14642:
----------------------------------------
Although the new mojo doesn't automate the version bump, it makes it explicit, obvious
and mandatory. For the last weeks, developers who have seen the mojo failure seem to
understand what to do and apply the necessary changes without problem. That was the most
valuable part.
We can leave this issue open to track idea about how to bump versions more easily; but I
don't think it's worth more effort (it's not a difficult or long task,
it's not error-prone thanks to Tycho checks, and there is already a maven mojo that
does that), so I'd rather close it.
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: Task
Components: build
Affects Versions: 4.1.0.Beta1
Reporter: Denis Golovin
Assignee: Max Rydahl Andersen
Labels: versioning
Fix For: 4.3.x
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
(v6.3.11#6341)