| workspace when skipping project selection [message #1508517] |
Fri, 12 December 2014 13:35  |
 Alexander Nittka
Messages: 1193
Registered: July 2009 |
Senior Member |
|
|
Hi,
I want to set the problems view configuration via a resource creation task even if I skip the project selection - I will have a workspace, after all. However, the variable ${workspace.location} is not known in this case.
Is there a way to enforce a "workspace task" in the user setup? Or is there a way to prevent the resource creation task from being triggered if no project is selected (I do not want to enter workspace.location every time and I don't want to create a variable that will possibly create a conflict)?
Alex
Need training, onsite consulting or any other kind of help for Xtext?
Go visit http://xtext.itemis.com or send a mail to xtext@itemis.de
|
|
|
|
|
| Re: workspace when skipping project selection [message #1510930 is a reply to message #1510763] |
Sun, 14 December 2014 13:47  |
Ed Merks
Messages: 33264
Registered: July 2009 |
Senior Member |
|
|
Alex,
I think one problem is that although there is a workspace.setup, a
synthesized one has no reference to any project.setup and hence no
project catalog is in scope, which is where the workspace task is
defined. Maybe we need something much like the "self" product version
for the empty project stream or synthesize a workspace task...
Note that in advanced properties you can set triggers so that a type of
task that could potentially run in bootstrap only runs in the IDE. So
no, all variables need not be known before bootstrapping, but the wizard
does generally prompt for variables that would otherwise need prompting
in the started IDE (so that the installation/provisioning process
doesn't block twice)...
On 14/12/2014 11:27 AM, Alexander Nittka wrote:
> Hi Eike,
>
> thanks for the tip with the variables. I guess this allows me to
> formulate the current problem even more clearly.
> With "osgi.instance.area" I have the same problem as with
> "workspace.location". Both variables are undeclared when starting the
> installer, I guess because the workspace location cannot be known at
> that point - at least not if no project is selected. Only with the
> project selection, the catalog's default setup entries are picked up -
> the ones that determine the workspace location.
>
> Am I correct when stating the following: The variable substitution is
> not lazy. All values must be known before bootstrapping. So it is not
> enough that osgi.instance.area would be known during the startup phase
> (when the new eclipse instance is actually started).
> As a consequence, it is currently impossible to achieve what I am
> trying to do!?
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: workspace when skipping project selection [message #1513517 is a reply to message #1510930] |
Tue, 16 December 2014 16:02 |
Alexander Nittka
Messages: 1193
Registered: July 2009 |
Senior Member |
|
|
Thanks to both of you for your replies and the great work you are doing.
From Ed's reply I understand that the problem is even more involved than I thought. For now, I will go the easy way (which I had not thought of before): I will create an empty project and add it to the user projects and select that instead of skipping the project selection.
This will allow me to make use of *all* the nice defaults provided by the eclipse project catalog without any pitfalls.
Alex
Need training, onsite consulting or any other kind of help for Xtext?
Go visit http://xtext.itemis.com or send a mail to xtext@itemis.de
|
|
|
Powered by
FUDForum. Page generated in 0.03961 seconds
] 
Search
Help
Register
Login
Home
