[JBoss JIRA] (JBDS-3718) Detected/selected JDK always reported as invalid
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3718?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-3718:
--------------------------------
> 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
> Priority: Blocker
> Labels: havoc
> Fix For: 9.1.0.GA
>
>
> 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
[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:
--------------------------------
Status: New (was: New)
Target Release: 9.1.0.GA
> 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
> Priority: Blocker
> Labels: havoc
> Fix For: 9.1.0.GA
>
>
> 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
[JBoss JIRA] (JBDS-3764) Installer - Component Detection - Fails to recognize JDK as previously installed by the same installer
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3764?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3764:
--------------------------------
Status: New (was: New)
Target Release: 9.1.0.GA
> Installer - Component Detection - Fails to recognize JDK as previously installed by the same installer
> ------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3764
> URL: https://issues.jboss.org/browse/JBDS-3764
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Environment: Installer: Setup-bundled-0.0.2-20160401-33
> Reporter: Len DiMaggio
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: havoc
> Fix For: 9.1.0.GA
>
> Attachments: JDK_detection.png
>
>
> See attached screenshot.
> To recreate this issue:
> * Install using installer: Setup-bundled-0.0.2-20160401-33, accept all defaults
> * Attempt to install "over" the installation just completed by running the installer a 2nd time
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3748) Installer - We need to define/document the minimum hardware requirements for the installer (and packages installed by the installer)
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3748?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3748:
-------------------------------------
More accurate calculation for required disk space:
* Installer 1.6G
* Installer unpacks contents to temp folder + 1.6G
* Target Folder after installation 2.7G
* Copy of virtual machine image in C:\Users\eskimo\.vagrant.d\boxes\cdkv2\0\virtualbox + 1G
* Virtual machine files in C:\Users\eskimo\VirtualBox VMs\rhel-ose_default_1460383456479_40322 + 3.5G
It is about 10G of disk space taken right after installation.
Then JBDS starts and creates workspace + 0.2G.
Windows should have enough free space on disk for swap file minimum/maximum file size recommended is RAM size/3 x RAM size, so medium would be 2 x RAM Size.
User also needs space for sources + 5G.
Considering all these numbers I would suggest:
1. Minimum configuration:
8G RAM;
10G + 2 * 8G + 5G = 31G;
CPU Intel i3 2GHz
2. Recommended configuration:
16G RAM;
10G + 2 * 16G + 5G = 47G;
CPU Intel i5 2GHz or better
> Installer - We need to define/document the minimum hardware requirements for the installer (and packages installed by the installer)
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3748
> URL: https://issues.jboss.org/browse/JBDS-3748
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: documentation, installer
> Affects Versions: 9.1.0.GA
> Reporter: Len DiMaggio
> Assignee: Misha Ali
> Labels: havoc
> Fix For: 9.1.0.GA
>
>
> The latest information that I can find for JBDS is:
> https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu...
> This is not adequate for the CDK, etc.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-657) Fuse EA tooling cannot be installed from central
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBTIS-657?page=com.atlassian.jira.plugin.... ]
Fred Bricon resolved JBTIS-657.
-------------------------------
Resolution: Done
Should be fixed by now. Please close/reopen Red Hat Central, Fuse should only show up if EA is enabled now (or already installed)
> Fuse EA tooling cannot be installed from central
> ------------------------------------------------
>
> Key: JBTIS-657
> URL: https://issues.jboss.org/browse/JBTIS-657
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 4.3.0.CR1
> Reporter: Jan Richter
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.3.0.Final
>
>
> It fails with the following message:
> {noformat}Cannot complete the install because one or more required items could not be found.
> Software being installed: JBoss Fuse Tooling JMX Bundles 8.0.0.Beta2-v20160401-1305-B821 (org.fusesource.ide.jmx.feature.feature.group 8.0.0.Beta2-v20160401-1305-B821)
> Missing requirement: JBoss Fuse Tooling JMX Bundles 8.0.0.Beta2-v20160401-1305-B821 (org.fusesource.ide.jmx.feature.feature.group 8.0.0.Beta2-v20160401-1305-B821) requires 'org.eclipse.gemini.management 2.0.0.RELEASE' but it could not be found{noformat}
> and this is in the error log:
> {noformat}HTTP Server 'Gateway Timeout': https://devstudio.jboss.com/targetplatforms/jbdsistarget/9.0.1.Final-SNAP...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years