|Re: VariableTask inconsistent behavior [message #1806446 is a reply to message #1806445]
||Thu, 09 May 2019 08:14
| Ed Merks
Registered: July 2009
1. The value of the variable must come from somewhere if it's used in some task...|
2. If it's used in a task, then when reviewing the tasks, you can see what value is being used. That value must come from somewhere. So look closely at the EclipseIni tasks on the confirmation page. Is that task present? What value does it show? If it's not present, you can still see it if you select to show all triggered tasks (and it will be disabled).
3. You can set the storage URI to scope://Installation so that it's only stored in the installation that's been created and will be prompted again for each different installation.
4. The variable with its user-assigned value will be stored somewhere, either the user.setup, the installation.setup, or the workspace.setup. It absolutely must be stored somewhere, otherwise the user would be prompted again for it when they launch their installation. I suspect it's stored in the user.setup, restricted to the project in which you've defined the variable in the setup.
You can run the installer with these VM arguments:
If you're on Windows you can use the latest installer form https://wiki.eclipse.org/Eclipse_Installer and run it with -vmargs followed by these arguments on the command line. On the other OSes you'll have to modify the eclipse-inst-ini. This will run the installer in a clean environment with an empty user home folder just like any first time user will experience. That absolutely should prompt the for variable, and if you give it some funky bogus value, you can search the fake home folder for that value to see where it stored.
Powered by FUDForum
. Page generated in 0.02758 seconds