|OOMPH startup: location of the "source" .setup file that corresponds to an Eclipse install [message #1810304]
||Wed, 07 August 2019 10:03
| Cristian Spiescu
Registered: July 2009
We are successfully using this great product in order to have a centralized eclipse config (plugins + workspace preferences) across our team. Yesterday I have made an update to the "source" .setup file, which resides on a SAMBA network share. This morning about 10 instances of eclipse were correctly updated, except one. Regarding this issue, I have 2 main questions:
1) Can the log level be modified, in order to have a more verbose output in: configuration\org.eclipse.oomph.setup\setup.log? For example I see entries that try to apply some settings. But I don't see entries regarding the attempt to download the new .setup file, make a diff and decide that: yes there are actions to perform or not.
2) And speaking of the "source" .setup file of the eclipse installation (which in our case sits on a network share): where is this path stored? I didn't find in the eclipse dir or in the workspace. I did find a mention in USER_HOME\.eclipse\org.eclipse.oomph.setup\setups\user.products.setup. But I think the entries here are used by the installer to keep a history that can be proposed in the combo box.
2.1) Is there maybe an UI that can display/alter this setting?
After several attempts of restarting eclipse, eventually the lat "lazy" Eclipse instance did correctly update. But I don't understand why it didn't work at the beginning and then, out of the blue why it did work. I'm wondering if a possible factor may have been that the Internet connection was down during a certain period. However the file was located in our intranet. Maybe at startup, OOMPH tries to communicate with the repositories on the Internet where the plugins are located. And no Internet => time outs, etc.
Thanks in advance!
Powered by FUDForum
. Page generated in 0.01883 seconds