[JBoss JIRA] (JBIDE-21175) [CDK] Require better logic to find vagrant.exe / vagrant command
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-21175:
-----------------------------------
Summary: [CDK] Require better logic to find vagrant.exe / vagrant command
Key: JBIDE-21175
URL: https://issues.jboss.org/browse/JBIDE-21175
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: openshift, server
Affects Versions: 4.3.1.Beta1
Reporter: Rob Stryker
First step to support for windows is properly locating vagrant.exe. This isn't a windows-only issue, though, as [~mmalina] has already commented that his vagrant was in /usr/local/bin/vagrant rather than /usr/bin/vagrant
So this is a concern on all OSes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21164) cdk server adapter shows error then overridden by adbinfo output
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21164?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21164:
-------------------------------------
> A) why was my username/password listed in plain text ? (might be basic vagrant issue not specific to cdk server adapter)
Seems you found the reason for this (linked issue)
> B) why did output of adbinfo override output from vagrant. should this not be appended or handled separately ?
It launched a new external process command. I can probably hide this in some fashion.
> cdk server adapter shows error then overridden by adbinfo output
> ----------------------------------------------------------------
>
> Key: JBIDE-21164
> URL: https://issues.jboss.org/browse/JBIDE-21164
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
>
> started cdk from server adapter view.
> starts up - eventually it fails and output contains my username and password in plain text and some error ...then replaced by output of adbinfo.
> A) why was my username/password listed in plain text ? (might be basic vagrant issue not specific to cdk server adapter)
> B) why did output of adbinfo override output from vagrant. should this not be appended or handled separately ?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21173) Runtime detection not working for CDK 2 Beta3
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21173?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21173:
-------------------------------------
I'll leave the issue open for now, but I don't expect any coding changes here. There's pretty much no way to tell a CDK Vagrantfile from any random vagrant file that has nothing to do with cdk. The .cdk marker is the way we've decided how to detect the cdk, and we're working to ensure that the jbds installer has the marker. Fred's idea to get the openshift-vagrant repo to also include the marker is also a great help.
> Runtime detection not working for CDK 2 Beta3
> ---------------------------------------------
>
> Key: JBIDE-21173
> URL: https://issues.jboss.org/browse/JBIDE-21173
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> When I point runtime detection to my cdk folder, it will not detect anything.
> I had the openshift.cdk feature installed.
> {code}
> nattura:features rasp$ ls|grep cdk
> org.jboss.tools.openshift.cdk.feature_3.1.0.Beta1-v20151202-0847-B100
> {code}
> And the runtime detection preference page shows that it will search for cdk runtimes
> (CDK is checked).
> The cdk in the folder that I use work fine when I add the adapter manually.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months