| [SOLVED] Application of properties from a project setup file to a running IDE instance [message #1722489] |
Fri, 05 February 2016 04:35  |
Eclipse User |
|
|
|
In my inital project setup file I enabled the line number ruler:
<?xml version="1.0" encoding="UTF-8"?>
<setup:PreferenceTask
xmi:version="2.0"
xmlns:xmi="had_to_remove_this_link_before_posting"
xmlns:setup="http://www.eclipse.org/oomph/setup/1.0"
key="/instance/org.eclipse.ui.editors/lineNumberRuler"
value="true">
<description>Show line numbers on the left side of editors.</description>
</setup:PreferenceTask>
I installed my development environment using this project setup. The project setup file is consumed from a central location. So any changes in the project setup file can be seen by my development environment.
Later on the line number ruler setting was changed from "true" to "false" in the project setup file.
Now I would expect that this change is also reflected in my installed development environment instance. But that's not the case, even if I run the setup task trigger manually.
Am I missing something or is this use case not supported by Oomph?
Thanks,
Chris
[Updated on: Fri, 05 February 2016 06:15] by Moderator |
|
|
|
|
| Re: Application of properties from a project setup file to a running IDE instance [message #1722505 is a reply to message #1722502] |
Fri, 05 February 2016 05:31  |
| Eclipse User |
|
|
|
Christoph,
Yes, the different scopes have different precedence, i.e., Product
Catalog, Product, Product Version, Project Catalog, Project, Stream,
User, Installation, Workspace. And many tasks are designed to either
override or merge when they apparent in multiple scopes. Obviously you
can only have one possible setting for the line-numbers preference, so
the tasks from the different scopes will override each other, in
precedence order.
As such, the user can always override tasks either for all installations
and all workspaces in their user.setup, for a specific installation in
that installation's installation.setup, or for a specific workspace in
that workspace's workspace.setup.
On 05.02.2016 11:11, Christoph Zauner wrote:
> Hi Eike,
>
> I have outlined the current behaviour below:
>
> - Project setup file: false
> - User setup file: true
> - Eclipse preferences dialog: true
>
> ===> Setup task not triggered / setting in the preference dialog is
> not changed
>
> - Project setup file: false
> - User setup file: - (I deleted this entry using the Oomph editor)
> - Eclipse preferences dialog: true
> ===> Setup task triggered / setting in the preference dialog is changed
>
> It seems that as long as the preference in the user setup exists the
> state recorded in the project setup file is not applied...
>
>
> Thanks,
> Chris
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.25459 seconds
Home
) for the hints! The problem was that a lot of preference tasks in my project setup file were already present in my user setup file. I must have put them accidentally there.