[jbosstools-issues] [JBoss JIRA] (JBDS-3695) Using existing JBDS with downloaded/installed JDK fails if JBDS is in Program Files folder

[Denis Golovin (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13180116#comment-13180116 ] 

Denis Golovin commented on JBDS-3695:
-------------------------------------

That means we need elevated privileges for installer itself. That would require for user to response to only one request to elevate priviliges. Now there are at least two requests. On comes from VirtualBox installer and another one from Vagrant. Privileges elevation triggers windows system dialog that contains Name of executable file and Publisher. In order to have publisher as Red Hat, Inc. the executable file must have digital signature.

> Using existing JBDS with downloaded/installed JDK fails if JBDS is in Program Files folder
> ------------------------------------------------------------------------------------------
>
>                 Key: JBDS-3695
>                 URL: https://issues.jboss.org/browse/JBDS-3695
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>          Components: installer
>    Affects Versions: 9.1.0.CR1
>            Reporter: Jan Richter
>            Assignee: Denis Golovin
>              Labels: havoc
>
> So if the user selects an existing JBDS installation from their Program Files folder and lets us install JDK, the installation will fail when the installer tries to change jbdevstudio.ini to point to the JDK we installed.
> The problem once again is in windows magic, it does not allow to modify files in a protected folder without administrative rights.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)