|
Re: Use default preferences for a workspace [message #1747305 is a reply to message #1747269] |
Fri, 11 November 2016 20:20 |
Eclipse User |
|
|
|
If you set defaults preferences in the DefaultScope, which is programmatic, then you shouldn't need to do anything.
But I'm guessing you want to provide different defaults for this customer. The best I can think of is to have your preference initializer check and load a properties file specified via a system property on the command-line, and use it to over-ride your defaults when setting the DefaultScope.
|
|
|
|
|
Re: Use default preferences for a workspace [message #1748423 is a reply to message #1747413] |
Wed, 23 November 2016 01:01 |
Eclipse User |
|
|
|
Your usecase might actually be a better use of the org.eclipse.ui.startup extension point.
The problem with using a bundle activator is that it requires that bundle to be somehow activated. So you have to be very certain that there is no circumstance where your customer can launch the application and somehow not trigger this bundle.
|
|
|
Powered by
FUDForum. Page generated in 0.03366 seconds