[ https://issues.jboss.org/browse/JBIDE-22459?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22459: ------------------------------------- Pasting notes from http://etherpad.corp.redhat.com/dcpmultiversion {quote} A) DCP1 vs DCP2 * DCP1 hard to maintain, DCP2 things can be changed. Used in two places: Eclipse Help Search (low priority) JBoss Central (higher priority) Options: 1) keep dcp1 alive for 3+ years 2) make dcp2 output dcp1 format for 3+ years output has changed because of upgrade of elasticsearch. limited resources since Lukas Vlcek. left, dcp in maintenance mode so far. Idea: could we have a "transforming" proxy that converts dcp2 json to dcp1 json. should be trivial. 3) we "fake" dcp1 by having a static page somewhere that gets updated once in a while. Suggest: we just make devstudio 9.1 use a static output - do changes in devstudio 10. B) EAP 7 quickstarts multiversion have been downprioritized: not on Ray and Harry's radar. Paul - look into how hard it can be done ? let us known Wednesday lunch time. Paul's Observations: Realistically we will not have multi-version support in JBD and thus DCP1 data. Also, we will need to update the JBD EAP Quickstarts to v7 (and thus the DCP1 data). Therefore, I don't see an outcome where JBDS 9 isn't showing only v7 quickstarts for EAP. Fred's Idea: Cache the results for EAP 6 and redirect the JBDS 9 code to get that. Potentially, we could cache the EAP 6 results prior to the DCP1 data being changed to have EAP 7 quickstarts. After this change, take another snapshot of the data. Merging these two snapshots results in a multi-version snapshot to provide to JBDS 9. Only give JBDS 9 multi-version support if JBDS 10 also gets this support. Otherwise a regression is created. {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)