[
https://issues.jboss.org/browse/JBIDE-18837?page=com.atlassian.jira.plugi...
]
Fred Bricon edited comment on JBIDE-18837 at 11/27/14 4:40 PM:
---------------------------------------------------------------
So after a chat with Max we agreed that :
- micro version lock was not necessary
- moving the version string to a different plugin than foundation is not practical
- we need to enforce foundation dependency at the minor level (X.Y), in all plugins
consuming foundation, i.e. central and examples for now.
- all micro releases should use the same config in ide-config.properties, i.e. once the
first GA is released, we should always find key|context|X.Y properties
- we need to create tests that would run daily and that check that :
** there are no unused keys in ide-config.properties (to catch typos)
** all urls defined there are live
was (Author: fbricon):
So after a chat with Max we agreed that :
- micro version lock was not necessary
- moving the version string to a different plugin than foundation is not practical
- we need to enforce foundation dependency at the minor level (X.Y), in all plugins
consuming foundation, i.e. central and examples for now.
- all micro releases should use the same config in ide-config.properties, i.e. once the
first GA is released, we should always find key|context|X.Y properties
- we need to create tests that would run daily and that check that :
* there are no unused keys in ide-config.properties (to catch typos)
* all urls defined there are live
because Foundation defines the version of JBoss Tools used to do
ide-config.properties lookup, must enforce it's always updated
-------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-18837
URL:
https://issues.jboss.org/browse/JBIDE-18837
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, central, common/jst/core, project-examples
Affects Versions: 4.2.1.CR1
Reporter: Nick Boldt
Fix For: 4.3.0.Alpha1
When updating from 4.2.0 to 4.2.1, a user might decide to only update Central or Project
Examples, and NOT update Foundation.core, which means his Eclipse will still think
it's 4.2.0, not 4.2.1, and he might get the wrong version of central/examples.
Therefore we need manifest-level [4.2.1,) requirements on upstream foundation.core in
examples and central, to force this lock-step updating.
And we need to use the maven enforcer plugin to fail the build if these versions get out
of sync.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)