[
https://issues.jboss.org/browse/JBIDE-25837?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-25837:
-------------------------------------
Really good catch on this one. I got so used to clicking through it I forgot to analyze
whether it should be showing so often.
Issue is in jbt-base. It seems after detecting things, it persists the detected runtimes
in some preference key so that it doesn't need to re-scan everything. It wasn't
persisting some additional information (the properties field mostly) in this cached xml,
so it wasn't able to use those later when deciding whether the runtimes exist yet or
not.
I'm skeptical of this architecture entirely, but, I don't think I'd be able to
change it any time soon. Either way, I've fixed that bug, to persist the properties.
CDK detected again after devstudio restart
------------------------------------------
Key: JBIDE-25837
URL:
https://issues.jboss.org/browse/JBIDE-25837
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdk, runtime-detection
Affects Versions: 4.5.3.AM3
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.5.3.Final
Attachments: cdk-repetitive-detection.png
This is basically why I saw JBIDE-25836 in the first place (Windows overlapping when
selecting a quick fix in runtime detection dialog).
I had an installation of devstudio and as usual, cdk server adapter was automatically
there. That's expected - when I install devstudio and start it, runtime detection will
notice ~/.minishift exists and will quietly create a server adapter with minishift binary
location missing.
Then I installed updates and restarted the IDE. On the next start, I was shown the
runtime detection dialog - it showed cdk (based on existing ~/.minishift) and it show an
error that minishift binary is missing. This seems to be a bug - there was no new server
found, only the existing cdk adapter.
!cdk-repetitive-detection.png!
I checked again on a clean installation and was able to reproduce easily - a simple IDE
restart will do. See the steps to reproduce.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)