[JBoss JIRA] (JBIDE-24676) CDK3 server adapter's console view is using wrong coding on all platforms
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24676?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24676:
---------------------------------------
It seems it's now happening on all platforms. I just saw it with cdk 3.1.0 on mac:
{code}
Starting local OpenShift cluster using 'virtualbox' hypervisor...
Registering machine using subscription-manager
[37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m [37m|[0m [37m/[0m [37m-[0m [37m\[0m Registration successful [31.2s]
-- Checking OpenShift client ... OK
-- Checking Docker client ... OK
-- Checking Docker version ... OK
-- Checking for existing OpenShift container ...
Deleted existing OpenShift container
-- Checking for registry.access.redhat.com/openshift3/ose:v3.5.5.31 image ... OK
-- Checking Docker daemon configuration ... OK
-- Checking for available ports ... OK
-- Checking type of volume mount ...
Using nsenter mounter for OpenShift volumes
-- Creating host directories ... OK
-- Finding server IP ...
Using 192.168.99.100 as the server IP
-- Starting OpenShift container ...
Starting OpenShift using container 'origin'
Waiting for API server to start listening
OpenShift server started
-- Removing temporary directory ... OK
-- Checking container networking ... OK
-- Server Information ...
OpenShift server started.
The server is accessible via web console at:
https://192.168.99.100:8443
To login as administrator:
oc login -u system:admin
{code}
> CDK3 server adapter's console view is using wrong coding on all platforms
> -------------------------------------------------------------------------
>
> Key: JBIDE-24676
> URL: https://issues.jboss.org/browse/JBIDE-24676
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.5.0.AM2
> Environment: Windows, Linux, macOS
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
> Attachments: Console_output.png, cdk_console_coding.png
>
>
> Console view on windows needs to set up proper coding. See the pic.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24796) Starting of CDK 3 Server Adapter with Minishift Home that differs from ~/.minishift prevents OS tooling to create proper connection and links it to default project
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24796?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24796:
---------------------------------------
The patch fixes what you described - changes to minishift home in server editor are persisted and visible as env vars in the launch config.
Now let's see if it actually works:
It starts ok, but then it fails to recognize the openshift user to use. So it will use openshift-dev which I believe is hardcoded in the tooling as a default - arguably the default should change to reflect openshift 3. But at least it helped me notice this :)
So it seems to me that when your tooling looks for the config file, it doesn't use the minishift home string.
> Starting of CDK 3 Server Adapter with Minishift Home that differs from ~/.minishift prevents OS tooling to create proper connection and links it to default project
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24796
> URL: https://issues.jboss.org/browse/JBIDE-24796
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.0.Final
> Environment: Fedora
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Critical
> Attachments: cdk3_sa-manual_correct-mhome.png, cdk3_sa-manual_wrong-mhome2.png
>
>
> In the first case I would understand that if you change you minishift home (in server editor) and then you start server adapter, you will get some mess... Although, I would like to see a validation of minishift home here. We are checking minishit binary, why not to check minishift home (in this case for existence of the folder). See
> !cdk3_sa-manual_wrong-mhome2.png|thumbnail!
> In the second case comes the bug. Even if I have set MINISHIFT_HOME folder, called setup-cdk that configured everything in that folder and put this folder as Minishift Home, CDK3 Server Adapter is not respecting that location. Or it is maybe OS tooling, not sure here. Solution here would be a check that verifies minishift's home set in CDK server editor corresponds with the one that minishift binary uses, if it is possible (from the side of binary) - but that seems not to be an option here as minishift/cdk stored everything in config that resides in MINISHIFT_HOME or ~/.minishift folder. See
> !cdk3_sa-manual_correct-mhome.png|thumbnail!
> Cc: [~adietish] [~rob.stryker].
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4444) [DevSuite Installer] Move Account step after Confirmation step
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4444?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-4444.
-----------------------------
Closing as done.
> [DevSuite Installer] Move Account step after Confirmation step
> --------------------------------------------------------------
>
> Key: JBDS-4444
> URL: https://issues.jboss.org/browse/JBDS-4444
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 11.0.0.AM1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: New_and_noteworthy, ui
> Fix For: 11.0.0.GA
>
> Attachments: RHDS_Installer_RHDAccountLoginScreen_Aug6-2017.jpg, about-background.png, about-update1.png, account-final-2.png, devsuite-installer-1.4.0-workflow.png, devsuite-installer-2.0.0-workflow.png, install-step-3-1.png, install-step-3-2.png, install-step-4.png, install-step-5-1.png, install-step-5-2.png, install-step-6-1.png, install-step-6.png, install-step1-final.png, install-step2.png
>
>
> As a user I would like to avoid entering login/password on a first page of installer, so I can explore and see what can be installed and then provide my credentials if I decided to proceed with installation.
> Current workflow is
> !devsuite-installer-1.4.0-workflow.png|thumbnail!
> should be transformed to
> !devsuite-installer-2.0.0-workflow.png|thumbnail!
> This would require to change starting page to show only generic information about DevSuite Installer and whole first page 'Account' should appear after confirmation page in case any of Red Hat Products is selected for installation.
> Here are screenshots for how it could look like for scenario when Red Hat Product Selected:
> !install-step1-final.png|thumbnail! !install-step2.png|thumbnail! !install-step-3-1.png|thumbnail! !install-step-4.png|thumbnail! !install-step-5-2.png|thumbnail! !install-step-6-1.png|thumbnail!
> and when community or 3rd party components only selected:
> !install-step1-final.png|thumbnail! !install-step2.png|thumbnail! !install-step-3-2.png|thumbnail! !install-step-5-1.png|thumbnail! !install-step-6.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months