Setting CDT preferences [message #533848] |
Mon, 17 May 2010 05:14  |
Eclipse User |
|
|
|
I'm trying to use the "setpref" buckminster command to disable CDT
indexing when I'm running my junit tests, but cannot seem to figure out
the correct way to do that.
I tried disabling indexing in my workspace, and then exporting the
preferences. The resulting prefs.xml has a line
> /instance/org.eclipse.cdt.core/indexer/indexerId=org.eclipse .cdt.core.nullindexer
but I cannot figure out how to translate that into something which the
"setpref" command accepts. For example, the following does not work:
> setpref /instance/org.eclipse.cdt.core/indexer/indexerId=org.eclipse .cdt.core.nullindexer
Buckminster complains:
> No preference matches /instance/org.eclipse.cdt.core/indexer/indexerId
--
/Jesper
|
|
|
Re: Setting CDT preferences [message #533920 is a reply to message #533848] |
Mon, 17 May 2010 09:35   |
Eclipse User |
|
|
|
Hi Jesper,
The setpref command is implemented for a limited number of preferences.
It's not intended as a generic tool to set arbitrary prefs. The reasons are:
1. There's just no way to anticipate what kind of preferences that
different bundles add and in what scope they are added. This in
combination with the fact that preferences often are tightly coupled
(only specific combinations are allowed) makes it impossible to create a
safe mechanism.
2. The mechanism that provides the "safe preference combinations" is
most often implemented in the preference editors. It cannot be called on
from a headless application.
3. It's relatively easy to create an empty workspace using your IDE,
define all the preferences using various preference editors, zip it up,
and then use it as a template workspace and use that as the base for
your build.
HTH,
Thomas Hallgren
On 05/17/2010 11:14 AM, Jesper Eskilson wrote:
>
> I'm trying to use the "setpref" buckminster command to disable CDT
> indexing when I'm running my junit tests, but cannot seem to figure out
> the correct way to do that.
>
> I tried disabling indexing in my workspace, and then exporting the
> preferences. The resulting prefs.xml has a line
>
>> /instance/org.eclipse.cdt.core/indexer/indexerId=org.eclipse .cdt.core.nullindexer
>>
>
> but I cannot figure out how to translate that into something which the
> "setpref" command accepts. For example, the following does not work:
>
>> setpref
>> /instance/org.eclipse.cdt.core/indexer/indexerId=org.eclipse .cdt.core.nullindexer
>>
>
> Buckminster complains:
>
>> No preference matches /instance/org.eclipse.cdt.core/indexer/indexerId
>
>
|
|
|
Re: Setting CDT preferences [message #533943 is a reply to message #533920] |
Mon, 17 May 2010 10:15  |
Eclipse User |
|
|
|
On 2010-05-17 15:35, Thomas Hallgren wrote:
> Hi Jesper,
>
> The setpref command is implemented for a limited number of preferences.
> It's not intended as a generic tool to set arbitrary prefs. The reasons
> are:
>
> 1. There's just no way to anticipate what kind of preferences that
> different bundles add and in what scope they are added. This in
> combination with the fact that preferences often are tightly coupled
> (only specific combinations are allowed) makes it impossible to create a
> safe mechanism.
>
> 2. The mechanism that provides the "safe preference combinations" is
> most often implemented in the preference editors. It cannot be called on
> from a headless application.
>
> 3. It's relatively easy to create an empty workspace using your IDE,
> define all the preferences using various preference editors, zip it up,
> and then use it as a template workspace and use that as the base for
> your build.
Ok, thanks.
--
/Jesper
|
|
|
Powered by
FUDForum. Page generated in 0.03408 seconds