[JBoss JIRA] (JBDS-3742) Cygwin setup executable should be installed as well
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/JBDS-3742?page=com.atlassian.jira.plugin.... ]
Pavol Pitonak updated JBDS-3742:
--------------------------------
Summary: Cygwin setup executable should be installed as well (was: Cygwin setup exdecutable should be installed as well)
> Cygwin setup executable should be installed as well
> ---------------------------------------------------
>
> Key: JBDS-3742
> URL: https://issues.jboss.org/browse/JBDS-3742
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Hardy Ferentschik
> Priority: Minor
> Labels: havoc
> Fix For: 9.1.0.GA
>
>
> As part of the installer Cygwin gets installed. However, the setup executable and package manager of Cygwin does not seem to get copied as well. Without it the user won't be able to extend/change the Cygwin configuration.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3747) Build failures with newest JSPM
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/JBDS-3747?page=com.atlassian.jira.plugin.... ]
Pavol Pitonak updated JBDS-3747:
--------------------------------
Priority: Minor (was: Major)
> Build failures with newest JSPM
> -------------------------------
>
> Key: JBDS-3747
> URL: https://issues.jboss.org/browse/JBDS-3747
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Jan Richter
> Priority: Minor
> Labels: havoc
> Fix For: 9.1.0.GA
>
>
> The newest JSPM release (0.16.32 atm.) has broken the build. We have reverted to 0.16.31 until a more permanent solution is discovered. Investigate the failures with newer versions.
--
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 commented on JBDS-3695:
-------------------------------------
This will be fixed with self extracting archive, because it triggers privilege lifting dialog.
> 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-3718) Detected/selected JDK always reported as invalid
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3718?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3718:
--------------------------------
Fix Version/s: 9.1.0.CR1
> Detected/selected JDK always reported as invalid
> ------------------------------------------------
>
> Key: JBDS-3718
> URL: https://issues.jboss.org/browse/JBDS-3718
> 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.CR1
>
>
> The installer correctly detects a JDK but still reports it as invalid. Same goes for selecting an installation of JDK - all checks pass but still the message says the installation is invalid.
> It does not seem to be a problem with the detection logic - it returns correct values for me. My guess would be that something is incorrectly propagated to the UI, but I haven't been able to find the source yet.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years