[JBoss JIRA] (JBDS-3812) Target folder input looks weird
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3812?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3812:
--------------------------------
Sprint: devex #118 July 2016
> Target folder input looks weird
> -------------------------------
>
> Key: JBDS-3812
> URL: https://issues.jboss.org/browse/JBDS-3812
> 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, ui
> Fix For: 10.1.0.AM3
>
> Attachments: selected.png, unselected.png
>
>
> There are a few visual issues with the target folder input group that make it look really weird:
> - When not focused, there is no real border around the input box, just a little line on the bottom
> - The Browse button is shoved right on top of the input field - when the field is focused, its border is hidden under the button on the right
> - The input field should probably be auto-focused
> - When the validation message shows an error, it has a red icon with black text
> - The path with spaces warning has black text - plus since this path is not allowed, it should show as error, not a warning
> - The message that folder will be created looks exactly like a warning, it should be styled as info (no orange text and icon)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[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:
--------------------------------
Sprint: devex #118 July 2016
> 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
> Fix For: 10.1.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
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBDS-3728) Assign IDs to UI elements
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3728?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3728:
--------------------------------
Sprint: devex #118 July 2016
> Assign IDs to UI elements
> -------------------------
>
> Key: JBDS-3728
> URL: https://issues.jboss.org/browse/JBDS-3728
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: platform-installer
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc, ui
> Fix For: 10.1.0.AM3
>
>
> The use of IDs greatly improves the lookup times and makes automated testing a lot easier. So please do include IDs in elements you create + we should add them to already existing elements that don't have any.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBDS-3624) Error while parsing response from auth server
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3624?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3624:
--------------------------------
Sprint: devex #118 July 2016
> Error while parsing response from auth server
> ---------------------------------------------
>
> Key: JBDS-3624
> URL: https://issues.jboss.org/browse/JBDS-3624
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Reporter: Pavol Pitonak
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.1.0.AM3
>
> Attachments: auth-error.png
>
>
> # npm start
> # type "asdf" to username field
> # type "asdf" to password field
> # open dev tools (Ctrl + Shift + i on Linux)
> # click "Log in" button
> result:
> This stack trace appears in console log:
> {code}
> SyntaxError: Unexpected token I
> at Object.parse (native)
> at fromJson (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:1274:14)
> at defaultHttpResponseTransform (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:9463:16)
> at file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:9554:12
> at forEach (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:343:20)
> at transformData (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:9553:3)
> at transformResponse (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:10322:21)
> at processQueue (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:14795:28)
> at file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:14811:27
> at Scope.$eval (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:16055:28)
> {code}
> JSON.parse failes because the server returned "Invalid user credentials for user asdf"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[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 updated JBDS-3701:
--------------------------------
Sprint: devex #118 July 2016
> 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: havoc
> Fix For: 10.1.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
(v6.4.11#64026)
9 years, 8 months