Open dougbreaux opened 11 months ago
Can you give us the .log from your workspace folder please?
This behavior continues and is consistent every time I start Eclipse. Is there some secure way to provide my .log file? In case there's anything sensitive in it.
Let me have a go at reproducing first if that is a potential issue.
@dougbreaux Hello Doug, I think we are missing some information here and are unable to reproduce the issue. Let me go through my reproduction steps and please tell me where your steps differ (note that this is only looking at the runtime being lost at the moment to reduce complexity):
How does your recreation differ ?
Dialog from step 3:
Additional, possibly-relevant detail: I have defined the usr directory as a location external to the product installations. So that I don't lose configuration when I upgrade:
Okay my apologies you did say "Liberty Developer Tools" not "Open Liberty Tools" I did try originally with the "WebSphere Developer Tools" which includes "Liberty Developer Tools" and the tradtional "WebSphere Tools" ... will try those notes and see if I can get any closer.
F3 on the server definition just brings up the server overview which is how I thought you got to the edit options.
Still happening on an entirely new system, but where I'd copied the workspace over from my prior system.
Trying to get to the bottom of this, I find a couple of files in workspace > .metadata > .plugins > org.eclipse.core.runtime > .settings
that do contain the obsolete paths:
com.ibm.ws.st.ui.prefs
org.eclipse.wst.server.core.prefs
Manually cleaning up these does seem to have resolved the problem. So, the question is why they're not being preserved when the represented settings are edited from within Eclipse.
Oh, including making the vm-install-id
in the second match the <vm id
in org.eclipse.jdt.launching.prefs
. Selecting the VM in the dialog apparently doesn't update this file either.
Well, I just added a new location from the UI, and I see it updated in the com.ibm.ws.st.ui.prefs
file. I'll have to see if it persists on shutdown/restart
Upon restart, ui.prefs kept the full list, but core.prefs reverted to the prior default
Eclipse 2023-06 currently, but has been occurring on earlier versions for at least a year. "IBM Liberty Developer Tools 23.1" (earlier last year). Semeru JDK 11. Windows.
Both the Liberty installation directory and the selected runtime revert back to their initial values rather than retaining the last ones I'd set and saved. Even when the original directory or runtime no longer exist.
I'll attach some screenshots and messages from both an instance I recorded 2022-10 and today, 2023-09.
2022-10
2023-09