[
https://issues.jboss.org/browse/JBIDE-24215?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-24215:
-------------------------------------
Steps to Reproduce:
# ASSERT: have 2 different cdk3 binaries (ex. Beta and Beta3), have a symlink pointing to
one of them
# ASSERT: have a cdk3 server adapter pointing to binary that the symlink doesnt point to
# EXEC: open CDK3 server adapter editor and hit "Browse" for the "Minishift
Location"
# EXEC: choose the symlink
Result:
"Minishift Location" shows the binary that the symlink points to, not the
symlink file. This means that I can't change the symlink and have the adapter using
the new binary. This basically voids the purpose of symlinks.
was:
# ASSERT: have 2 different cdk3 binaries (ex. Beta and Beta3), have a symlink pointing to
one of them
# ASSERT: have a cdk3 server adapter pointing to binary that the symlink doesnt point to
# EXEC: open CDK3 server adapter editor and hit "Browse" for the "Minishift
Location"
# EXEC: choose the symlink
Result:
"Minishift Location" will show the binary that the symlink points to, not the
symlink file. This means that I cant change the symlink and have the adapter using the new
binary with voids the purpose of symlinks
CDK Server adapter editor: using symlink for "Minishift
Location" stores the referenced binary, not the symlink
---------------------------------------------------------------------------------------------------------------
Key: JBIDE-24215
URL:
https://issues.jboss.org/browse/JBIDE-24215
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdk, openshift
Affects Versions: 4.4.4.AM2
Reporter: Andre Dietisheim
Assignee: Rob Stryker
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)