[
https://issues.jboss.org/browse/JBIDE-18261?page=com.atlassian.jira.plugi...
]
Mickael Istria edited comment on JBIDE-18261 at 9/4/14 7:34 AM:
----------------------------------------------------------------
Scenario I have in mind is:
* JBT-IS has version 1.0.0.GA on central
* JBT-IS has a milestone 1.0.1.CR1 on earlyaccess
then we want early access to win, and when JBT-IS 1.0.1 goes GA, cental only is updated,
then we have
* JBT-IS 1.0.1.GA on central
* JBT-IS 1.0.1.CR1 on early access
So we want Cental to win.
The idea was that software sources could be updated independently.
was (Author: mickael_istria):
Scenario I have in mind is:
* JBT-IS has version 1.0.0.GA on central
* JBT-IS has a milestone 1.0.1.CR1 on earlyaccess
then we want early access to win, and when JBT-IS 1.0.1 goes GA, then we have
* JBT-IS 1.0.1.GA on central
* JBT-IS 1.0.0.CR1 on early access
So we want Cental to win.
The idea was that software sources could be updated independently.
When connectors have same ids, priority should be given to
early-access
-----------------------------------------------------------------------
Key: JBIDE-18261
URL:
https://issues.jboss.org/browse/JBIDE-18261
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central
Affects Versions: 4.2.0.CR1
Reporter: Mickael Istria
Assignee: Mickael Istria
Labels: respin-a
Fix For: 4.2.0.CR1
Assuming we have 2 discoveyr connectors with same IDs (example of AngularJS vs
AngularJS+Ionic), then when both are visible, priority should be given to the one which is
early access.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)