[JBoss JIRA] (JBDS-3609) update splashscreen, about gfx, start icon for developers.redhat.com
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3609?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3609:
----------------------------------
Invalid file format for the splash image - must be a 24-bit bmp.
> update splashscreen, about gfx, start icon for developers.redhat.com
> --------------------------------------------------------------------
>
> Key: JBDS-3609
> URL: https://issues.jboss.org/browse/JBDS-3609
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: build, installer, p2-product
> Reporter: Max Rydahl Andersen
> Assignee: James Cobb
> Priority: Blocker
> Fix For: 10.0.0.Alpha1
>
> Attachments: about-jbds10.png, launcher-icons-jbds10.png, RedHat_JBDS.zip, splash-jbds10.png
>
>
> update splashscreen, about gfx, start icon for developers.redhat.com
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3766) Installer - Seeing an intermittent issue where vagrant fails to start - is a system restart needed as indicated in the vagrant log?
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3766?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3766:
--------------------------------
Fix Version/s: 10.0.1.Alpha1
(was: 10.0.0.GA)
> Installer - Seeing an intermittent issue where vagrant fails to start - is a system restart needed as indicated in the vagrant log?
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3766
> URL: https://issues.jboss.org/browse/JBDS-3766
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Environment: Installer: Setup-bundled-0.0.2-20160401-33
> Reporter: Len DiMaggio
> Assignee: Denis Golovin
> Priority: Critical
> Labels: havoc
> Fix For: 10.0.1.Alpha1
>
> Attachments: install.log, Is_Restart_Needed.png, vagrant.log, vbox.log
>
>
> See attached log files.
> After some install attempts, Vagrant fails to start. The vagrant install log reports the following:
> {code}
> MSI (s) (DC:C4) [11:00:34:591]: Product: Vagrant -- Installation completed successfully.
> MSI (s) (DC:C4) [11:00:34:591]: Windows Installer installed the product. Product Name: Vagrant. Product Version: 1.7.4. Product Language: 1033. Manufacturer: HashiCorp. Installation success or error status: 0.
> MSI (s) (DC:C4) [11:00:34:591]: Windows Installer requires a system restart. Product Name: Vagrant. Product Version: 1.7.4. Product Language: 1033. Manufacturer: HashiCorp. Type of System Restart: 2. Reason for Restart: 2.
> MSI (s) (DC:C4) [11:00:34:591]: Product: Vagrant. Restart required. The installation or update for the product required a restart for all changes to take effect. The restart was deferred to a later time.
> {code}
> Is a system restart needed to ensure that the vagrant installation is successful on Windows?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[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 resolved JBDS-3718.
---------------------------------
Resolution: Duplicate Issue
> Detected/selected JDK always reported as invalid
> ------------------------------------------------
>
> Key: JBDS-3718
> URL: https://issues.jboss.org/browse/JBDS-3718
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.0.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)
9 years, 10 months
[JBoss JIRA] (JBDS-3753) Installer forces using detected JDK, tries to install JBDS with the bundled Java anyway
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3753?page=com.atlassian.jira.plugin.... ]
Denis Golovin resolved JBDS-3753.
---------------------------------
Resolution: Out of Date
> Installer forces using detected JDK, tries to install JBDS with the bundled Java anyway
> ---------------------------------------------------------------------------------------
>
> Key: JBDS-3753
> URL: https://issues.jboss.org/browse/JBDS-3753
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Environment: Setup-bundled-0.0.2-20160401-28
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.0.0.GA
>
>
> Using bundled installer build 28 - confirmation page will not let me use the bundled JDK if it detects a pre-existing JDK somewhere else.
> Once the installation is triggered, JDK goes straight to finished (not a problem under these circumstances) but JBDS fails right away and the log says:
> {noformat}
> Fri, 01 Apr 2016 07:20:44 GMT-INFO: jbds - Execute c:\DeveloperPlatform\jdk8\bin\java.exe -DTRACE=true,-jar,C:\Users\jbossqa\AppData\Local\Temp\7zSE006.tmp\jbds.jar,C:\Users\jbossqa\AppData\Local\Temp\jbds-autoinstall.xml
> Fri, 01 Apr 2016 07:20:44 GMT-ERROR: jbds - Error: spawn c:\DeveloperPlatform\jdk8\bin\java.exe ENOENT
> Fri, 01 Apr 2016 07:20:44 GMT-ERROR: jbds -
> Fri, 01 Apr 2016 07:20:44 GMT-ERROR: jbds failed to install: Error: spawn c:\DeveloperPlatform\jdk8\bin\java.exe ENOENT
> {noformat}
> So basically, I can't get it to install the bundled JDK but it will still try to use it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months