| OOMPH startup: location of the "source" .setup file that corresponds to an Eclipse install [message #1810304] |
Wed, 07 August 2019 10:03  |
 Cristian Spiescu
Messages: 100
Registered: July 2009 |
Senior Member |
|
|
Hello,
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!
Regards,
Cristian
|
|
|
| Re: OOMPH startup: location of the "source" .setup file that corresponds to an Eclipse ins [message #1810315 is a reply to message #1810304] |
Wed, 07 August 2019 15:36  |
Ed Merks
Messages: 33133
Registered: July 2009 |
Senior Member |
|
|
1) No there is currently no support for other types of logging. The setup log only logs the activities of tasks as they perform and is part of the setup task performer. The loading of resources (setup files) happens before any of that kicks in. Setups that are loaded from the internet (http/https) are cached in ~/.eclipse/org.eclipse.oomph.setup/cache and if there is a network failure the cached version is used instead of the freshly downloaded version.
2) All setups must be reachable from the index. So if you use Navigate -> Open Setup -> Parent Models -> Catalog Index your setup must be found in that tree. If it's a project setup, it will be either in your own product catalog or one of the user extensions to one of the exist project catalog. But it sounds like you have a product setup? The user.products.setup is just a place holder in the index referenced like this from the index: <productCatalog
href="user-ext:/user.products.setup?class='http://www.eclipse.org/oomph/setup/1.0%23//ProductCatalog',name='user.products',label='%3CUser%20Products%3E',description='A%20container%20catalog%20for%20local%20user-defined%20products'#/"/>
Selection history is maintained by catalogs.setup...
2.1) I'm not sure what you are wanting to alter. But all setups are reachable from the index. (Other than the history setups.)
And yes, if there are network failures, historical versions will be used (for http/https) access. If file: is used, those are not cached and failures will cause the setups not to be loaded and nothing to be done. No communication is done with p2 repositories other than by the tasks themselves. Loading setups of course happens prior to that.
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.63342 seconds
] 
Search
Help
Register
Login
Home
