[
https://issues.jboss.org/browse/JBIDE-14642?page=com.atlassian.jira.plugi...
]
Denis Golovin edited comment on JBIDE-14642 at 2/23/15 1:59 PM:
----------------------------------------------------------------
I'll leave it open for now, because It is not exactly what was requested in this
issue:
1. Have a dedicated build for version verification
2. Document the how to use tool like this
It is good to have it but sometimes it makes problems like:
1. impossible to verify that unchanged components are compilable in new stream without
upversioning. Is there any option do disable this verification?
2. Extra downloading for verification for every build even if version was updated in the
beginning of next development stream and no checks are needed anymore.
was (Author: dgolovin):
I'll leave it open for now, because It is not exactly what was requested in this
issue:
1. Have a dedicated build for version verification
2. Document the how to use tool like this
It is good to have it but sometimes it makes problems like:
1. impossible to verify that unchanged components are compilable in new stream without
upversioning. Is there any option do disable this verification?
2. Extra downloading for verification for every build even if version was updated in the
beginning of next development stream and no check are needed anymore.
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.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)