April 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3832) Investigate if one can find if a pre-installed virtualbox also contains network drivers

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3832?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3832: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > Investigate if one can find if a pre-installed virtualbox also contains network drivers > --------------------------------------------------------------------------------------- > > Key: JBDS-3832 > URL: https://issues.jboss.org/browse/JBDS-3832 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: ui > Fix For: 10.4.0.GA > > > In order to start CDK we need Virtualbox with its networking support installed. Since the vbox installer allows the users to only install the bare VM, we should find a way to tell if the vbox network drivers have been installed in the detected installation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3642) Installer is too opaque - need a debug/verbose mode to track progress and debug failures

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3642?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3642: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > Installer is too opaque - need a debug/verbose mode to track progress and debug failures > ---------------------------------------------------------------------------------------- > > Key: JBDS-3642 > URL: https://issues.jboss.org/browse/JBDS-3642 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: ui > Fix For: 10.4.0.GA > > > The install.log created by the installer does not contain a detailed listing of all actions performed by the installer. Setting the install browser into a debug mode ( "set PDKI_DEBUG=true" ) generated additional information, but it is still node a detailed dump of all actions. Can we add a debug/verbose/trace mode? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4309) Include Kompose in DevSuite Installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4309?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4309: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > Include Kompose in DevSuite Installer > ------------------------------------- > > Key: JBDS-4309 > URL: https://issues.jboss.org/browse/JBDS-4309 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Reporter: Sudhir Verma > Assignee: Sudhir Verma > Labels: New_and_noteworthy, Sprint_Demo > Fix For: 10.4.0.GA > > > Release to include is https://github.com/kubernetes-incubator/kompose/releases/tag/v0.4.0 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4247) Replace 7Zip self extracting executable

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4247?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4247: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > Replace 7Zip self extracting executable > --------------------------------------- > > Key: JBDS-4247 > URL: https://issues.jboss.org/browse/JBDS-4247 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.3.0.AM2 > Environment: Windows > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.4.0.GA > > > Implement simple installer based on [go-bindata:https://github.com/jteeuwen/go-bindata]. > It would do simple thing similar to other self-extracting installers, unpack specific Asset from executable and run it. > In case of windows installer it would speedup installation. because instead of extracting everything for bundle installer as 7Zip does, it would pull only installer first and run it. Then every specific installer selected for installation would first pull data out of installer executable with go-bindata. > This approach would fix several opened issues that should be addressed upstream in 7Zip selexecuatble. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3931) Installed OC binary is not used by default if user has another OC already on system path

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3931?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3931: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > Installed OC binary is not used by default if user has another OC already on system path > ---------------------------------------------------------------------------------------- > > Key: JBDS-3931 > URL: https://issues.jboss.org/browse/JBDS-3931 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 10.4.0.GA > > > I tried to install everything on a machine where an existing OC binary was already on path. The newly installed devstudio then used it by default instead of the bundled one. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3631) When an install fails, the user is able to view the error log to debug the cause of the failure, but the UI does not display any details

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3631?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3631: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > When an install fails, the user is able to view the error log to debug the cause of the failure, but the UI does not display any details > ---------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3631 > URL: https://issues.jboss.org/browse/JBDS-3631 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc, ui > Fix For: 10.4.0.GA > > Attachments: install_error.png > > > It would be helpful to provide the user either a summary of the last failure, or a window that displays the install log, inside the installer UI. Thx! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3871) installer credentials misleading/incomplete information.

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3871?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3871: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > installer credentials misleading/incomplete information. > -------------------------------------------------------- > > Key: JBDS-3871 > URL: https://issues.jboss.org/browse/JBDS-3871 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.Beta1 > Environment: Win 7/64 bit > Reporter: Robert Terzi > Assignee: Denis Golovin > Priority: Minor > Labels: ui > Fix For: 10.4.0.GA > > > There are several problems a with the information on the platform installer's login screen: > # "Your developers.redhat.com credentials" is misleading, Should probably be "Your Red Hat username" to be consistent with RHDeveloper registration process. > # The register link points to the login page, not the register page. > # Registering on RHDevelopers isn't sufficient. (A registered user gets " Terms and Conditions for CDK have not been signed." > # There should probably be a link to a page on RHDev with more info/FAQ about credentials, the registration process, and obtaining a (no-cost) subscription. > The platform installer description of the credentials to use are misleading. Currently it says " Try it now by providing your developers.redhat.com credentials to get access." > Users can log into RHDevelopers via other accounts (github, linkedin, stack overflow, etc. using OAUTH). They can not log into access.redhat.com (the customer portal) or other Red Hat sites with their developer.redhat.com "credentials". > During registration on RHDevelopers, a simple developers account is created. (Note: At this point, a Red Hat username hasn't been created yet. > Currently, when the user clicks a download link that goes through RHDev download manager, their account is "upgraded", which creates a Red Hat user than can be used to log into RHCP. Terms & conditions are presented. A no-cost RHEL Developer suite subscription is added to the user's Red Hat account. > Their Red Hat username and password which could be different from the RHDeveloper credentials. They will need their Red Hat username for the CDK box to attach to their subscription. Without it the CDK box won't start up correctly as it can't download software. > Some of this is covered for external users in the No-cost RHEL Dev. Suite FAQ. http://developers.redhat.com/articles/no-cost-rhel-faq/ We might need to do a version of that for CDK and JBDS platform installer.. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4016) Add Readme.txt(.md) in the root of devsuite installation with references to all included projects

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4016?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4016: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > Add Readme.txt(.md) in the root of devsuite installation with references to all included projects > ------------------------------------------------------------------------------------------------- > > Key: JBDS-4016 > URL: https://issues.jboss.org/browse/JBDS-4016 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.4.0.GA > > > This file should be generated during build based on info in platform specific requirements*.json -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4326) When hyper-v installed virtualization detection does not work

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4326?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4326: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > When hyper-v installed virtualization detection does not work > ------------------------------------------------------------- > > Key: JBDS-4326 > URL: https://issues.jboss.org/browse/JBDS-4326 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.4.0.AM2 > Environment: Windows > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.4.0.GA > > Attachments: hyperv-virtualisation-is-not-detected.png > > > When hyper-v installed, powershell script we use to detect virtualization is enabled in bios always returns false. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3956) Installer should let to update detected oracle virtualbox

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3956?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3956: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > Installer should let to update detected oracle virtualbox > --------------------------------------------------------- > > Key: JBDS-3956 > URL: https://issues.jboss.org/browse/JBDS-3956 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.1.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.4.0.GA > > > It should also work for OpenJDK installed from .msi file. Detection should read installation information from registry using vbs scripts (see https://msdn.microsoft.com/en-us/library/aa369767(v=vs.85).aspx for details). > Reading install information form registry would work better than detection based on environment variables. It would let rerun detection on installer windows activation and detect changes in configuration without restarting installer. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2017