[jbosstools-issues] [JBoss JIRA] (JBIDE-21194) Result from adbinfo on windows has different syntax

[Rob Stryker (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-21194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker resolved JBIDE-21194.
---------------------------------
    Resolution: Done


I'm not exactly sure how to answer this question.  We're running "vagrant adbinfo" which does not actually export the environment variables. It instructs the USER to export them.  Otherwise we'd need to run something like "vagrant adbinfo | sh" 

Furthermore, this won't modify the environment variables of already running processes.  So the eclipse environment wont ever actually be updated at any point, and the "vagrant adbinfo" or "vagrant adbinfo | sh" type processes will already be terminated and thus have no environment. 

I suppose I *could* run "vagrant adbinfo | sh" and then run a NEW simple java program which sysouts all environment variables, the way jdt launching does to determine what version fo the VM belongs to what execution envuronment, but that seems extremely circular logic and very wrong to me. 

The fact is, there's no way for me to simply execute adbinfo and have the eclipse environment updated. It will only update new processes, not processes that already have an enviuronment. 

> 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)