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

[Jan Richter (JIRA)]

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

Jan Richter commented on JBDS-3695:
-----------------------------------

How exactly can this duplicate an issue that was reported later (and is generally unrelated)? Anyway, since the 7zip archive requires admin privileges and JBDS detection was dropped for this release, I'd say this issue is outdated more than a duplicate.

> 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
>             Fix For: 9.1.0.GA
>
>
> 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)