|Re: Using oomph's setup project model on a shared Install [message #1764983 is a reply to message #1759536]
||Mon, 05 June 2017 13:14
| Stuart Websper
Registered: April 2017
Thanks for the previous reply. Sorry I haven't got back to you earlier but I was taken off my current project for a while.
Anyway I had a look at your answer and it seems I already have the installation.setup file moved to the psuedo installation directory, so I am not sure this is the answer.
Now, I am afraid the whole oomph implementation is way over my head, So maybe I should go back over my requirements.
Basically , in the past we have used workspace mechanic plugin,but it seems that oomph is the modern way of handling the synchronisation of preferences
Basically, when a user starts an instance of the shared install eclipse, I want each user to be able to pick up the common configuration setup (a file in our source code repository) and it to be applicable for all workspaces created for that install. Essentially, what the file user.home/.eclipse/org.eclipse.oomph.setup/setups/user.setup currently achieves, but for a specified path in my source checkout.
In the shared install case, the .eclipse and workspace folders are obviously created on the first execution of eclipse by the user. I was therefore hoping I could get oomph to somehow update the users instance of these folders to pick up the shared configuration at initialisation.
However, following the "Setup Project Model" workflow does not work for this use case as indicated in my first post. It only works for a private install where there is a single user.
Is there anyway I can get oomph to achieve my current objectives? Obviously I could change user.home/.eclipse/org.eclipse.oomph.setup/setups/user.setup for each user to be a symbolic link to the file in the repository checkout, but it feels like there should be a much more elegant way to achieve this built into oomph.
Any help would be greatly appreciated.
Powered by FUDForum
. Page generated in 0.01823 seconds