[
https://issues.jboss.org/browse/JBIDE-21194?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-21194:
---------------------------------------------
I have not suggested you are going to update the eclipse environment.
I'm saying that the output of adbinfo is out of your control and could (in theory)
start containing actually bash/batch code making your parsing broken.
Hence why simply doing a run of the script and dump the environment variables (which will
with guarantee not contain bash/batch code) you get something that is consistent and
easily parsable.
Also removes any need of windows/linux specific comment/variable escaping/parsing.
basically on linux/osx run `eval $(vagrant-adbinfo); export' and you should have
updated info in a properties key/value style list.
Same for windows run the output and run "SET" to get the list as a set of
key/value pairs.
Result from adbinfo on windows has different syntax
---------------------------------------------------
Key: JBIDE-21194
URL:
https://issues.jboss.org/browse/JBIDE-21194
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: openshift, server
Affects Versions: 4.3.0.Beta1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
The result from adbinfo on linux is:
{code}
export key=value
{code}
The result on Windows is:
{code}
setx key value
{code}
The adbinfo runner needs to be aware of this difference and react accordingly when
creating the openshift connection.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)