[JBoss JIRA] (JBDS-3695) Using existing JBDS with downloaded/installed JDK fails if JBDS is in Program Files folder
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3695?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-3695.
-----------------------------
Resolution: Out of Date
> 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)
10 years
[JBoss JIRA] (TOOLSDOC-708) JBDS 9.1 GA: Update support page with fedora and os x versions
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-708?page=com.atlassian.jira.plug... ]
Martin Malina commented on TOOLSDOC-708:
----------------------------------------
[~mhusnain], we also need to make sure Red Hat OpenJDK 8 is added to Windows for JBDS 9.1.
> JBDS 9.1 GA: Update support page with fedora and os x versions
> --------------------------------------------------------------
>
> Key: TOOLSDOC-708
> URL: https://issues.jboss.org/browse/TOOLSDOC-708
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Components: General documentation issues
> Affects Versions: 9.1 Beta2
> Reporter: Misha Ali
> Assignee: Misha Ali
> Labels: Support
> Fix For: 9.1 GA
>
> Attachments: screenshot_support.png, Screenshot_support_update.png
>
>
> We should update the support matrix of JBDS to include the latest Fedora releases: 22 and 23. At the same time, 21 can be dropped.
--
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 Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3695?page=com.atlassian.jira.plugin.... ]
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)
10 years
[JBoss JIRA] (JBDS-3677) Add Red Hat OpenJDK 8 on Windows to support matrix for JBDS
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3677?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-3677:
-------------------------------------
That is correct, thanks [~nickboldt].
[~mhusnain], can you make sure this is included in the support matrix for JBDS 9.1?
TOOLSDOC-708 contains a draft of changes for the support matrix document for JBDS 9.1 release, so perhaps this can be added.
> Add Red Hat OpenJDK 8 on Windows to support matrix for JBDS
> -----------------------------------------------------------
>
> Key: JBDS-3677
> URL: https://issues.jboss.org/browse/JBDS-3677
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements
> Affects Versions: 9.1.0.CR1
> Reporter: Martin Malina
> Assignee: Martin Malina
> Fix For: 9.1.0.GA
>
>
> Since a major use case for JBDS will be that users will install it using the big installer including Azul JDK on Windows, we need to make sure this combination is actually tested and supported.
> I guess nobody realized this before, but it seems pretty obvious that this is necessary.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3802) Add version detection and validation for installed vagrant and oracle virtualbox
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3802?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-3802.
-----------------------------
Verified with jboss-devstudio-platform-9.1.0-Beta1-20160416-130-installer.exe.
> Add version detection and validation for installed vagrant and oracle virtualbox
> --------------------------------------------------------------------------------
>
> Key: JBDS-3802
> URL: https://issues.jboss.org/browse/JBDS-3802
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer
> Affects Versions: 9.1.0.GA
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 9.1.0.GA
>
>
> Installer should detect installed vagrant using windows system utils and environment variables. Warning should be shown if the detected version is higher/lower than recommended. Installation cannot proceed if detected vagrant version number is lower than recommended, No messages shown is detected version is exact match for recomended
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3724) Installer: Update JBDS to 9.1.0.GA
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3724?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-3724.
-----------------------------
Verified with jboss-devstudio-platform-9.1.0-Beta1-20160416-130-installer.exe.
> Installer: Update JBDS to 9.1.0.GA
> ----------------------------------
>
> Key: JBDS-3724
> URL: https://issues.jboss.org/browse/JBDS-3724
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: installer
> Reporter: Alexey Kazakov
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: havoc
> Fix For: 9.1.0.GA
>
>
> We should make sure the installer consumes the proper JBDS bits.
> 1. It should be the latest nightly build until the 9.1.0 code freeze.
> 2. The CR1 build after the code freeze.
> 3. 9.1.0.GA build as soon as it's available.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3669) Inject version, timestamp and Jenkins build number into installer to show in installer window
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3669?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-3669.
-----------------------------
Verified with jboss-devstudio-platform-9.1.0-Beta1-20160416-130-installer.exe.
> Inject version, timestamp and Jenkins build number into installer to show in installer window
> ---------------------------------------------------------------------------------------------
>
> Key: JBDS-3669
> URL: https://issues.jboss.org/browse/JBDS-3669
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: installer
> Affects Versions: 9.1.0.Beta2
> Reporter: Denis Golovin
> Assignee: Nick Boldt
> Labels: havoc
> Fix For: 9.1.0.GA
>
> Attachments: JBDS3669-new-UI.png, version-string-in-exe-and-first-page-of-installer.png
>
>
> Currently this information is not available in installer at execution time, we should create json or js file with this info before executing the build, include it in installer and use during installation to get required data.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years