[
https://issues.jboss.org/browse/JBIDE-26909?page=com.atlassian.jira.plugi...
]
Ondrej Dockal commented on JBIDE-26909:
---------------------------------------
Cc: [~adietish] [~jeffmaury].
[~rob.stryker] Maybe you can bring some light here if this is good idea or there is
something behind what would stand against this. There is also another approach which would
mean contract testing on daily basis between crc API and what needed in studio. Have
agreement with folks from CRC team that would notify us any time they change some string
output does not seem optimal.
Refactor reading crc version to be more robust and resilient against
little string changes
------------------------------------------------------------------------------------------
Key: JBIDE-26909
URL:
https://issues.jboss.org/browse/JBIDE-26909
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: cdk
Affects Versions: 4.13.0.Final
Reporter: Ondrej Dockal
Priority: Major
Fix For: 4.14.x
As a follow up to JBIDE-26907 we would like to have more robust {code}crc version{code}
output parsing. Code
[
here|https://github.com/jbosstools/jbosstools-openshift/blob/master/plugi...].
--
This message was sent by Atlassian Jira
(v7.13.8#713008)