[
https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi...
]
Martin Malina edited comment on JBIDE-19697 at 4/30/15 5:11 AM:
----------------------------------------------------------------
So Radim Hopp came up with the idea that it could actually be Oomph that is doing this.
And it seems to be the case.
See the very first item of the Preference page of Preference Recorder:
!preference-recorder.png!
But even if I disable this in a brand new instance of Eclipse, it still happens - once I
install JBT, the config appears there and after Eclipse restart, I am offered to add those
runtimes :(
And I tried one more thing: I installed nightly build of JBoss Tools into Eclipse Mars M4
and in this case this doesn't happen - the config is not copied during the
installation. So I think Oomph is to blame (it's not present in M4).
was (Author: mmalina):
So Radim Hopp came up with the idea that it could actually be Oomph that is doing this.
And it seems to be the case.
See the very first item of the Preference page of Preference Recorder:
!preference-recorder.png!
But even if I disable this in a brand new instance of Eclipse, it still happens - once I
install JBT, the config appears there and after Eclipse restart, I am offered to add those
runtimes :(
org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir
during JBDS BYOE installation
--------------------------------------------------------------------------------------------------
Key: JBIDE-19697
URL:
https://issues.jboss.org/browse/JBIDE-19697
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: runtime-detection
Affects Versions: 4.3.0.Alpha2
Reporter: Martin Malina
Assignee: Snjezana Peco
Attachments: preference-recorder.png
When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace,
during the installation, suddenly the runtime detection config appears inside my Eclipse
isntall dir:
{code}
$ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'
Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs
{code}
This is inside the file:
{code}
$ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs
cat
eclipse.preferences.version=1
runtimePaths=<?xml version\="1.0" encoding\="UTF-8"
standalone\="no"?>\n<runtimePaths version\="2">\n
<runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0"
scanOnEveryStartup\="false" timestamp\="-1">\n
<serverDefinitions>\n <serverDefinition description\=""
enabled\="true"
location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP
6.3" type\="EAP" version\="6.3">\n <included/>\n
</serverDefinition>\n </serverDefinitions>\n
</runtimePath>\n</runtimePaths>\n
{code}
It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when
testing server tooling. But how did this happen?
I looked for the pref file before I started BYOE installation. Then a bit later, a few
minutes into the installation, I checked again and the file is there now.
Can somebody explain what's going on?
Note: This happened to me yesterday and it surprised me, but I wasn't sure if it
wasn't my mistake somehow. But Max preferred I try again, so I did. And it is
happening again now.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)