Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Oomph » Question about VariableTask precedence and <restriction>
Question about VariableTask precedence and <restriction> [message #1469347] Tue, 11 November 2014 14:19 Go to next message
Christian Damus is currently offline Christian DamusFriend
Messages: 1222
Registered: July 2009
Location: Canada
Senior Member

Hi,

I have a continual problem of forgetfulness in dealing with the
eclipse.target.platform variable, which I don't think should be my
problem. The problem is that every time I run the Setup tasks in my
Papyrus Mars development workbench, I have to remember to go back a
page in the wizard from where it starts, check the "Show all variables"
option, and change the value of the eclipse.target.platform from "Luna"
to "Mars". I have to do this every time, but I usually forget, and so
end up with a target platform full of Luna stuff instead of Mars stuff
and consequently a workspace full of compilation errors.

The question I have is Why is this necessary? I see in my user.setup
that this variable's value is "Luna", but I also see clearly in my
workspace.setup that the value there is "Mars". I had thought that any
variable values configured in workspace.setup would override the same
variables in user.setup. Is that not so? There is a <restriction>
element in my workspace.setup (see below) that I don't understand its
purpose, but it also seems to me like it would not interfere as it
appears to match my situation (I do set up from the project catalog
that it references).

I would hack the variable in my user.setup to evade this problem,
except that I do have another workspace for Papyrus Luna maintenance
that does use the Luna target platform.

Thanks,

Christian


=== From user.setup ===

<setupTask
xsi:type="setup:VariableTask"
name="eclipse.target.platform"
value="Luna"
defaultValue="None"
label="Target Platform">
<description>Choose the compatibly level for the target
platform.</description>
</setupTask>


=== From workspace.setup ===

<setupTask
xsi:type="setup:VariableTask"
name="eclipse.target.platform"
value="Mars"
defaultValue="None"
label="Target Platform">
<restriction
xsi:type="setup:ProjectCatalog"

href="index:/org.eclipse.setup#//@projectCatalogs[name='org.eclipse']"/>
<description>Choose the compatibly level for the target
platform.</description>
</setupTask>
Re: Question about VariableTask precedence and &lt;restriction&gt; [message #1469397 is a reply to message #1469347] Tue, 11 November 2014 15:14 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 31640
Registered: July 2009
Senior Member
Christian,

Comments below.

On 11/11/2014 3:19 PM, Christian W. Damus wrote:
> Hi,
>
> I have a continual problem of forgetfulness in dealing with the
> eclipse.target.platform variable, which I don't think should be my
> problem. The problem is that every time I run the Setup tasks in my
> Papyrus Mars development workbench, I have to remember to go back a
> page in the wizard from where it starts, check the "Show all
> variables" option, and change the value of the eclipse.target.platform
> from "Luna" to "Mars". I have to do this every time, but I usually
> forget, and so end up with a target platform full of Luna stuff
> instead of Mars stuff and consequently a workspace full of compilation
> errors.
That's crappy.
>
> The question I have is Why is this necessary?
Indeed a good question...
> I see in my user.setup that this variable's value is "Luna", but I
> also see clearly in my workspace.setup that the value there is "Mars".
We did change things a while back to stop saving these things in
restricted compounds within the user.setup...
> I had thought that any variable values configured in workspace.setup
> would override the same variables in user.setup. Is that not so?
No, the user the setup is last and overrides all...
> There is a <restriction> element in my workspace.setup (see below)
> that I don't understand its purpose, but it also seems to me like it
> would not interfere as it appears to match my situation (I do set up
> from the project catalog that it references).
>
> I would hack the variable in my user.setup to evade this problem,
> except that I do have another workspace for Papyrus Luna maintenance
> that does use the Luna target platform.
I think you should just get rid of it from your user.setup. That's not
where it's stored anymore. If any existing IDE/setup needs it and
doesn't yet have it in the workspace.setup, it will just prompt you...
>
> Thanks,
>
> Christian
>
>
> === From user.setup ===
>
> <setupTask
> xsi:type="setup:VariableTask"
> name="eclipse.target.platform"
> value="Luna"
> defaultValue="None"
> label="Target Platform">
> <description>Choose the compatibly level for the target
> platform.</description>
> </setupTask>
>
>
> === From workspace.setup ===
>
> <setupTask
> xsi:type="setup:VariableTask"
> name="eclipse.target.platform"
> value="Mars"
> defaultValue="None"
> label="Target Platform">
> <restriction
> xsi:type="setup:ProjectCatalog"
> href="index:/org.eclipse.setup#//@projectCatalogs[name='org.eclipse']"/>
> <description>Choose the compatibly level for the target
> platform.</description>
> </setupTask>
>
>


Ed Merks
Professional Support: https://www.macromodeling.com/
Re: Question about VariableTask precedence and &lt;restriction&gt; [message #1469428 is a reply to message #1469397] Tue, 11 November 2014 15:50 Go to previous message
Christian Damus is currently offline Christian DamusFriend
Messages: 1222
Registered: July 2009
Location: Canada
Senior Member

Thanks, Ed! I shall follow your recommendation.

Christian


On 2014-11-11 15:14:28 +0000, Ed Merks said:

> Christian,
>
> Comments below.
>
> On 11/11/2014 3:19 PM, Christian W. Damus wrote:
>> Hi,
>>
>> I have a continual problem of forgetfulness in dealing with the
>> eclipse.target.platform variable, which I don't think should be my
>> problem. The problem is that every time I run the Setup tasks in my
>> Papyrus Mars development workbench, I have to remember to go back a
>> page in the wizard from where it starts, check the "Show all variables"
>> option, and change the value of the eclipse.target.platform from "Luna"
>> to "Mars". I have to do this every time, but I usually forget, and so
>> end up with a target platform full of Luna stuff instead of Mars stuff
>> and consequently a workspace full of compilation errors.
> That's crappy.
>>
>> The question I have is Why is this necessary?
> Indeed a good question...
>> I see in my user.setup that this variable's value is "Luna", but I also
>> see clearly in my workspace.setup that the value there is "Mars".
> We did change things a while back to stop saving these things in
> restricted compounds within the user.setup...
>> I had thought that any variable values configured in workspace.setup
>> would override the same variables in user.setup. Is that not so?
> No, the user the setup is last and overrides all...
>> There is a <restriction> element in my workspace.setup (see below) that
>> I don't understand its purpose, but it also seems to me like it would
>> not interfere as it appears to match my situation (I do set up from the
>> project catalog that it references).
>>
>> I would hack the variable in my user.setup to evade this problem,
>> except that I do have another workspace for Papyrus Luna maintenance
>> that does use the Luna target platform.
> I think you should just get rid of it from your user.setup. That's not
> where it's stored anymore. If any existing IDE/setup needs it and
> doesn't yet have it in the workspace.setup, it will just prompt you...
>>
>> Thanks,
>>
>> Christian
>>
>>
>> === From user.setup ===
>>
>> <setupTask
>> xsi:type="setup:VariableTask"
>> name="eclipse.target.platform"
>> value="Luna"
>> defaultValue="None"
>> label="Target Platform">
>> <description>Choose the compatibly level for the target platform.</description>
>> </setupTask>
>>
>>
>> === From workspace.setup ===
>>
>> <setupTask
>> xsi:type="setup:VariableTask"
>> name="eclipse.target.platform"
>> value="Mars"
>> defaultValue="None"
>> label="Target Platform">
>> <restriction
>> xsi:type="setup:ProjectCatalog"
>> href="index:/org.eclipse.setup#//@projectCatalogs[name='org.eclipse']"/>
>> <description>Choose the compatibly level for the target platform.</description>
>> </setupTask>
Previous Topic:How to suppress the Questionnaire in automated tests?
Next Topic:How to set lot of Preferences in a setup model
Goto Forum:
  


Current Time: Sat Dec 05 13:00:46 GMT 2020

Powered by FUDForum. Page generated in 0.01721 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top