December 2017 - jbosstools-issues

[JBoss JIRA] (JBDS-3852) Mock installer model to allow running installer fast without installing anything

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3852?page=com.atlassian.jira.plugin.... ] Denis Golovin closed JBDS-3852. ------------------------------- Fix Version/s: 11.2.0.AM3 (was: 11.x) Resolution: Won't Fix > Mock installer model to allow running installer fast without installing anything > -------------------------------------------------------------------------------- > > Key: JBDS-3852 > URL: https://issues.jboss.org/browse/JBDS-3852 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: Havoc > Fix For: 11.2.0.AM3 > > > Would be good for demonstrations and UI development -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

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 closed JBDS-3871. ------------------------------- Fix Version/s: 11.2.0.AM3 (was: 11.x) Resolution: Done Moved to https://github.com/redhat-developer-tooling/developer-platform-install/is.... > 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: 11.2.0.AM3 > > > 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.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3746) Unable to access OpenShift console with MS Edge

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3746?page=com.atlassian.jira.plugin.... ] Denis Golovin closed JBDS-3746. ------------------------------- Fix Version/s: 11.2.0.AM3 (was: 10.x) Resolution: Out of Date Closing as 'Out of date', please reopen if it is still relevant. > Unable to access OpenShift console with MS Edge > ------------------------------------------------ > > Key: JBDS-3746 > URL: https://issues.jboss.org/browse/JBDS-3746 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: documentation, platform-installer, upstream > Environment: Windows 10 Pro > Reporter: Hardy Ferentschik > Labels: havoc > Fix For: 11.2.0.AM3 > > > On Windows 10 (Pro) after installing and starting the CDK development environment, one is not able to access the OpenShift console (https://10.1.2.2:8443/console) using Microsoft Edge. The IP of the host only network IP does not matter. Using a 192.168 address won't work either. > Using any other browser - IE, Chrome, Firefox - the console can be reached. It seems to be an Edge specific issue and may report the same issue: > * http://www.tenforums.com/installation-setup/8979-dont-forget-edge-can-acc... > * https://social.technet.microsoft.com/Forums/forefront/en-US/0face535-3c7a... > * https://www.google.se/search?q=edge+canot+acess+page&ie=utf-8&oe=utf-8&gw... > I tried several work-arounds, but none worked so far. If there were a confirmed workaround one could image the installer applying it (if possible). In this case we might want to add a warning somewhere in the installer or at least somewhere in the documentation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

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 closed JBDS-3931. ------------------------------- Resolution: Migrated to another ITS Migrated to https://github.com/redhat-developer-tooling/developer-platform-install/is... > 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: 11.2.0.AM3 > > > 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.5.0#75005)

8 years, 3 months

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: 11.2.0.AM3 (was: 11.x) > 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: 11.2.0.AM3 > > > 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.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4103) Install JDK and force usage of it for JBDS even if a JRE is available

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4103?page=com.atlassian.jira.plugin.... ] Denis Golovin closed JBDS-4103. ------------------------------- Resolution: Migrated to another ITS Migrated to https://github.com/redhat-developer-tooling/developer-platform-install/is... > Install JDK and force usage of it for JBDS even if a JRE is available > --------------------------------------------------------------------- > > Key: JBDS-4103 > URL: https://issues.jboss.org/browse/JBDS-4103 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Aurélien Pupier > Assignee: Denis Golovin > Fix For: 11.2.0.AM3 > > > When using JBDS, a lot of people will use Maven and having a JDK by default is better. > It allows to launch Maven install with java compilation directly, without extra configuration. > (as a side note, do we really want to set a vm in .ini? when the Vm is updated, the link is broken and we need to update it) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3948) Use CDK nightly builds metadata to include nightly CDK build into DevSuite Bundled Installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3948?page=com.atlassian.jira.plugin.... ] Denis Golovin closed JBDS-3948. ------------------------------- Resolution: Won't Fix > Use CDK nightly builds metadata to include nightly CDK build into DevSuite Bundled Installer > -------------------------------------------------------------------------------------------- > > Key: JBDS-3948 > URL: https://issues.jboss.org/browse/JBDS-3948 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.1.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 11.x > > > Nightly CDK builds have sha256 checksums and metadata.txt. DevSuite build should use that to check if new download for CDK resources is required. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4103) Install JDK and force usage of it for JBDS even if a JRE is available

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4103?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4103: -------------------------------- Fix Version/s: 11.2.0.AM3 (was: 11.x) > Install JDK and force usage of it for JBDS even if a JRE is available > --------------------------------------------------------------------- > > Key: JBDS-4103 > URL: https://issues.jboss.org/browse/JBDS-4103 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Aurélien Pupier > Assignee: Denis Golovin > Fix For: 11.2.0.AM3 > > > When using JBDS, a lot of people will use Maven and having a JDK by default is better. > It allows to launch Maven install with java compilation directly, without extra configuration. > (as a side note, do we really want to set a vm in .ini? when the Vm is updated, the link is broken and we need to update it) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3701) Add check for an existing Java to find if it is JRE or JDK

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3701?page=com.atlassian.jira.plugin.... ] Denis Golovin closed JBDS-3701. ------------------------------- Fix Version/s: 11.2.0.AM3 (was: 11.x) Resolution: Migrated to another ITS Migrated to https://github.com/redhat-developer-tooling/developer-platform-install/is... > Add check for an existing Java to find if it is JRE or JDK > ---------------------------------------------------------- > > Key: JBDS-3701 > URL: https://issues.jboss.org/browse/JBDS-3701 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: ui > Fix For: 11.2.0.AM3 > > > JBDS will run on both, but in order to develop something the user needs a JDK. The detection/selection will allow using JRE distribution of Java without even a warning. We should find out what kind of Java the user has selected and at least display a warning if it is not JDK (or just not allow JRE). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4448) JBDS install failure with no explanation

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4448?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4448: -------------------------------- Fix Version/s: 11.2.0.AM3 (was: 11.x) > JBDS install failure with no explanation > ----------------------------------------- > > Key: JBDS-4448 > URL: https://issues.jboss.org/browse/JBDS-4448 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.4.0.GA > Environment: Mac, using DevSuite installer 1.4.1 GA > Reporter: Bob Davis > Assignee: Denis Golovin > Priority: Critical > Fix For: 11.2.0.AM3 > > Attachments: Screen Shot 2017-06-26 at 2.09.01 PM.png, install.log > > > Installing RED HAT JBOSS DEVELOPER STUDIO10.4.0.GA failed, and no explanation or remediation such as "try again" or "remove ...", etc. was offered. The end user is stuck with no way out. > Additionally, the "next step" displayed is "Get Started", but there is no way to get there, no button to "Next", or any indication of how to move forward to it. > Quitting is the only option. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

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 December 2017