[JBoss JIRA] (JBDS-3633) Uninstaller does nothing
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3633?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3633:
--------------------------------
Fix Version/s: 10.0.0.Alpha1
(was: 9.1.0.GA)
> Uninstaller does nothing
> ------------------------
>
> Key: JBDS-3633
> URL: https://issues.jboss.org/browse/JBDS-3633
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.0.0.Alpha1
>
>
> Current implementation just removes record about installation from windows registry.
> What it should do:
> 1. Remove virtual box from vagrant:
> {code}vagrant box remove cdkv2{code}
> 2. Remove virtual machine from virtual box
> {code}vboxmanage --unregister ${vmname}{code}
> 3. Uninstall what was installed:
> vargant
> virtual box
> developer studio
> 4. Delete:
> CDK
> Open JDK 8
> 5. Cleanup PATH env variable
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3695) Using existing JBDS with downloaded/installed JDK fails if JBDS is in Program Files folder
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3695?page=com.atlassian.jira.plugin.... ]
Denis Golovin resolved JBDS-3695.
---------------------------------
Resolution: Duplicate Issue
> 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)
10 years
[JBoss JIRA] (JBDS-3695) Using existing JBDS with downloaded/installed JDK fails if JBDS is in Program Files folder
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3695?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-3695:
--------------------------------
> 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)
10 years
[JBoss JIRA] (JBDS-3695) Using existing JBDS with downloaded/installed JDK fails if JBDS is in Program Files folder
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3695?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3695:
--------------------------------
Status: New (was: New)
Target Release: 9.1.0.GA
> 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)
10 years
[JBoss JIRA] (JBDS-3695) Using existing JBDS with downloaded/installed JDK fails if JBDS is in Program Files folder
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3695?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3695:
-----------------------------
> 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)
10 years
[JBoss JIRA] (JBDS-3701) Add check for an existing Java to find if it is JRE or JDK
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3701?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3701:
--------------------------------
Fix Version/s: 10.0.0.Alpha1
(was: 9.1.0.GA)
> Add check for an existing Java to find if it is JRE or JDK
> ----------------------------------------------------------
>
> Key: JBDS-3701
> URL: https://issues.jboss.org/browse/JBDS-3701
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.0.0.Alpha1
>
>
> JBDS will run on both, but in order to develop something the user needs a JDK. The detection/selection will allow using JRE distribution of Java without even a warning. We should find out what kind of Java the user has selected and at least display a warning if it is not JDK (or just not allow JRE).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3697) Installed vagrant version in not validated against anything
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3697?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3697:
--------------------------------
Priority: Blocker (was: Major)
> Installed vagrant version in not validated against anything
> -----------------------------------------------------------
>
> Key: JBDS-3697
> URL: https://issues.jboss.org/browse/JBDS-3697
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: havoc
> Fix For: 9.1.0.GA
>
>
> It looks like the installer stores the version of a vagrant installation it finds/the user selects, but there is no value it would check it against. (Which is strange because I remember putting it into the code and the html file still references the fields which apparently don't exist anymore).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years