Home » Eclipse Projects » Oomph » Eclipse Installer, Windows standard user and User Account Control
| Eclipse Installer, Windows standard user and User Account Control [message #1698217] |
Fri, 12 June 2015 04:57  |
Eclipse User |
|
|
|
On my Windows machine, I usually work as standard user and not with administrator rights. With the new Eclipse Installer, I now have the following symptoms:
Having downloaded the latest version of the installer and started it in the advanced mode, the project catalog does not show the user projects I had added with the old Oomph-Installer; and trying to materialize projects that worked before fail with strange errors (NPE while trying determine the launcher name, "should not get here" error while trying to create a symbolic link when trying to clone a git repository).
I narrowed down the problem to the following. When starting the installer, I have to authorize the execution with an administrator password, because the installer changes settings (Windows User Account Control is activated). As a consequence, the installer runs within the administrator account and uses its settings (including project catalog) and also stores the task variables in the administrator's user.setup.
As long the original installation process is running (that is, also if the installed Eclipse is launched automatically), it seems to be in this strange administration mode...
The only workaround I found so far is the following. I run the installer without choosing the project I am interested in (I use my empty project instead so that the workspace is already in the correct location). Then I launch the installed Eclipse (not automatically, as mentioned before) and install the project using Import->Oomph... At this point, I do see the project catalog of the correct user and materialising the projects succeeds.
Am I doing something wrong, have you had other reports of related issues, am I the only one not running Windows as administrator...? It should not be a problem, if the "one-shot" Eclipse installer has to be run as Administrator, however if I switch to advanced mode and "copy" the installer to disk, couldn't *that* installer be like the old Oomph-Installer (which could be run without Administrator rights) or do you know why it is not?
... I have found a mode that works for me, but getting a project instantiated has become much more cumbersome. Also, the error messages did not help to narrow down the problem (not really Oomph's fault). And if others run into the same problem they may be more inclined to blaming Oomph (forecast based on current discussions concerning the preference recorder).
|
|
|
| Re: Eclipse Installer, Windows standard user and User Account Control [message #1698221 is a reply to message #1698217] |
Fri, 12 June 2015 06:08  |
| Eclipse User |
|
|
|
Am 12.06.2015 um 10:57 schrieb Alexander Nittka:
> On my Windows machine, I usually work as standard user and not with administrator rights. With the new Eclipse
> Installer, I now have the following symptoms:
>
> Having downloaded the latest version of the installer and started it in the advanced mode, the project catalog does
> not show the user projects I had added with the old Oomph-Installer;
That seems okay. They're *user* projects and it seems you had registered them as a different user.
> and trying to materialize projects that worked before fail with strange errors (NPE while trying determine the
> launcher name, "should not get here" error while trying to create a symbolic link when trying to clone a git repository).
Please submit a bugzilla and don't forget to attach the relevant stack traces.
> I narrowed down the problem to the following. When starting the installer, I have to authorize the execution with an
> administrator password, because the installer changes settings (Windows User Account Control is activated). As a
> consequence, the installer runs within the administrator account and uses its settings (including project catalog) and
> also stores the task variables in the administrator's user.setup.
> As long the original installation process is running (that is, also if the installed Eclipse is launched
> automatically), it seems to be in this strange administration mode...
I sounds a little as if Eclipse's secure storage is related but without stack traces it's hard to tell.
> The only workaround I found so far is the following. I run the installer without choosing the project I am interested
> in (I use my empty project instead so that the workspace is already in the correct location). Then I launch the
> installed Eclipse (not automatically, as mentioned before) and install the project using Import->Oomph... At this
> point, I do see the project catalog of the correct user and materialising the projects succeeds.
>
> Am I doing something wrong,
I don't think so. But I have no experience with Windows user access control.
> have you had other reports of related issues,
No, never.
> am I the only one not running Windows as administrator...?
I can't answer that ;-)
> It should not be a problem, if the "one-shot" Eclipse installer has to be run as Administrator, however if I switch to
> advanced mode and "copy" the installer to disk, couldn't *that* installer be like the old Oomph-Installer (which could
> be run without Administrator rights)
I do not recall that we changed something in either mode to make it not work without Administrator rights. Did something
change on your end when this started to happen?
> or do you know why it is not?
No, your stack traces might sched light on what goes on.
>
> .. I have found a mode that works for me, but getting a project instantiated has become much more cumbersome.
We certainly would like to fix that, but we rely on your precise input to reproduce the problem.
> Also, the error messages did not help to narrow down the problem (not really Oomph's fault).
Please mention the exact error messages in the bugzilla.
> And if others run into the same problem they may be more inclined to blaming Oomph (forecast based on current
> discussions concerning the preference recorder).
Yes, that's a general concern because Oomph integrates with so many other technologies. But what can we do ;-)
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
| | | | | |
Goto Forum:
Current Time: Sun Jul 13 17:26:19 EDT 2025
Powered by FUDForum. Page generated in 0.05441 seconds |
Home