June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3738) Getting Started / Readme for new users after Dev Platform install is complete

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3738?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3738: ---------------------------------- [~mhusnain] is this done for 9.1? Is it updated for 10.0.0? Can this be completed by EOD tomorrow Friday Jun 24? Need it ready before Summit on Monday. > Getting Started / Readme for new users after Dev Platform install is complete > ----------------------------------------------------------------------------- > > Key: JBDS-3738 > URL: https://issues.jboss.org/browse/JBDS-3738 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: documentation, platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Nick Boldt > Assignee: Misha Ali > Priority: Blocker > Labels: Havoc > Fix For: 10.0.0.GA > > > Per discussion today, we need some sort of README / Getting Started Guide for new CDK users. > This could be a link from the last page of the Dev Platform installer to a remote HTML page, but we could also include a copy of that HTML page in the c:\devplatform folder so people can refer to it offline. > Need to decide where to locate the page online. If the doc can be available before April 12, it could potentially be included in the output of the installer for offline use too. > URL: http://developers.redhat.com/devstudio-preview -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22594) Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22594?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22594: ------------------------------------- >From the OpenShift explorer, we know what connection we're on, when doing Deploy to OpenShift, so showing the 1st page doesn't make sense >From the Docker Explorer, we decided to have the current connection preselected and not show the 1st page because it's way more convenient. I really don't want to go back to that old behavior. Moreover, having multiple OpenShift connections to select from is really not gonna be a common use case, except for us developers and QE. So my vote is we keep the current behavior. Anyway, that's an orthogonal problem to the real issue here. If anything we should open a separate ticket to discuss it. I'm really curious to understand how we got that regression about the missing password for the CDK registry > Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22594 > URL: https://issues.jboss.org/browse/JBIDE-22594 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitry Bocharov > Labels: connection_wizard, deploy_docker_wizard, openshift_v3 > Fix For: 4.4.1.S116 > > Attachments: out-2.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22594) Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection

by Dmitry Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22594?page=com.atlassian.jira.plugi... ] Dmitry Bocharov commented on JBIDE-22594: ----------------------------------------- [~akazakov] yes, with the registry ones. Actually it is in the header of the JIRA :) : Deploy Docker Image wizard: *password/token for registry* is not prefilled even after choosing a connection > Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22594 > URL: https://issues.jboss.org/browse/JBIDE-22594 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitry Bocharov > Labels: connection_wizard, deploy_docker_wizard, openshift_v3 > Fix For: 4.4.1.S116 > > Attachments: out-2.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22594) Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22594?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-22594: ---------------------------------------- [~dbocharov] so, the issue was not with connection credentials as staid in the description of this issue but with the registry ones? I can reproduce it btw. Regarding first page vs second. I still believe we should always open the first page. [~fbricon], [~jeffmaury] any comments? > Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22594 > URL: https://issues.jboss.org/browse/JBIDE-22594 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitry Bocharov > Labels: connection_wizard, deploy_docker_wizard, openshift_v3 > Fix For: 4.4.1.S116 > > Attachments: out-2.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22594) Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection

by Dmitry Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22594?page=com.atlassian.jira.plugi... ] Dmitry Bocharov commented on JBIDE-22594: ----------------------------------------- [~akazakov], the thing that i could reproduce and have just fixed and almost ready to push it that if nothing selected in OS explorer, you "deploy to OS", choose connection, press next and have nothing in username/password/url for registry. About first wizard page - i agree, but have a look at the discussion of [~scabanovich] and [~fbricon] that i provided in my previous comment. They did it intentionally. Do i need to change it? > Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22594 > URL: https://issues.jboss.org/browse/JBIDE-22594 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitry Bocharov > Labels: connection_wizard, deploy_docker_wizard, openshift_v3 > Fix For: 4.4.1.S116 > > Attachments: out-2.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22642) ProcessInformationStore.loadprocessStore doesn't work on Windows

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22642?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-22642: -------------------------------------- Assignee: Rob Stryker [~rob.stryker] please review the PR. > ProcessInformationStore.loadprocessStore doesn't work on Windows > ---------------------------------------------------------------- > > Key: JBIDE-22642 > URL: https://issues.jboss.org/browse/JBIDE-22642 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.3.1.Final > Environment: Windows > Reporter: Aurélien Pupier > Assignee: Rob Stryker > > - l.90 it searches for a jps file although the file is jps.exe on Windows > jps = jHomePath.removeLastSegments(1).append("bin").append("jps").toFile(); > error log: > {noformat} > java.io.IOException: Cannot run program "C:\Program Files\Java\jdk1.8.0_65\jre\bin\jps": CreateProcess error=2, The system cannot find the file specified > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) > at java.lang.Runtime.exec(Runtime.java:620) > at java.lang.Runtime.exec(Runtime.java:485) > at org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore(ProcessInformationStore.java:102) > at org.jboss.tools.jmx.local.ProcessInformationStore.refreshProcessInformationStore(ProcessInformationStore.java:64) > at org.jboss.tools.jmx.local.ProcessInformationStore$1.run(ProcessInformationStore.java:140) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified > at java.lang.ProcessImpl.create(Native Method) > at java.lang.ProcessImpl.<init>(ProcessImpl.java:386) > at java.lang.ProcessImpl.start(ProcessImpl.java:137) > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22638) Cant start remote server on Win10

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22638?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-22638: ---------------------------------------- [~jeffmaury] can you translate the error message to English please? :) > Cant start remote server on Win10 > --------------------------------- > > Key: JBIDE-22638 > URL: https://issues.jboss.org/browse/JBIDE-22638 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > > ASSERT: create a local Wildfly server > ASSERT: create a remote (filesystem and shell operations controlled) using the same runtime and will local path > EXEC: start the remote server > ASSERT: the remote server won't start, the following lines are displayed in the console: > 'cmd' n'est pas reconnu en tant que commande interne > ou externe, un programme ex‚cutable ou un fichier de commandes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-323) Registry Account Unavailable In Preferences

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-323?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg commented on ERT-323: ------------------------------------- This should be fixed. I've added the update site for 2.0.0 to the Marketplace Entry : https://marketplace.eclipse.org/content/eclipse-docker-tooling > Registry Account Unavailable In Preferences > ------------------------------------------- > > Key: ERT-323 > URL: https://issues.jboss.org/browse/ERT-323 > Project: Eclipse Release Train > Issue Type: Bug > Components: Linux Tools > Affects Versions: Mars.2 (4.5), Neon (4.6) > Environment: Windows 7 Enterprise 64-bit > 64-bit Eclipse > Reporter: Trevor Trevor > Attachments: no_registry_account.png > > > According to the [user guide|https://wiki.eclipse.org/Linux_Tools_Project/Docker_Tooling/User_Guide] "By default, the Docker Hub registry will be used, however, a user may specify an additional private registry if desired. Additional registries are added using Windows -> Preferences -> Docker -> Registry Accounts." > However, the only things available under Docker are "Docker Machine," and "Logging"; "Registry Accounts" is not present. I have observed this on both Eclipse Neon and Mars, and on a different Windows 7 machine. The plugin does work to show containers and images, but this prevents me from being able to connect to private repository on my network. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22594) Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22594?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-22594: ---------------------------------------- Guys I can't reproduce this. If I don't have anything selected in the OS explorer then when I do "deploy to OS" on the image then the "Sing in to OS" page of the wizard is open where I can select the connection. But if I have selected a connection in the wizard already then the second "Deploy the Image" page is open. But I agree that even when I have some selection in the OS explorer it still can be confusing to the user. IMO we always should open the very first page of the wizard to make it clear to the user what connection we are going to use and make it's obvious for him/her how to select another one. > Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22594 > URL: https://issues.jboss.org/browse/JBIDE-22594 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitry Bocharov > Labels: connection_wizard, deploy_docker_wizard, openshift_v3 > Fix For: 4.4.1.S116 > > Attachments: out-2.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-323) Registry Account Unavailable In Preferences

by Trevor Trevor (JIRA)

[ https://issues.jboss.org/browse/ERT-323?page=com.atlassian.jira.plugin.sy... ] Trevor Trevor edited comment on ERT-323 at 6/23/16 11:47 AM: ------------------------------------------------------------- Docker Tooling was installed from the Eclipse Marketplace. Installed Software shows Docker Tooling 1.2.0. When looking at Plug-ins, I can actually see that version 2.0.0 was also installed. To be more precise, only the Docker Core Plugin 2.0.0 was installed, the UI Plug-in, Tooling Documentation are at 1.2.0, and the 1.2.0 core plugin was also installed. So, perhaps this is really an issue with installation from the Eclipse Marketplace and having started on Eclipse Mars, once an update is run, it is actually 2.0.0, and everything is happier. Edit: Added note: I did go to the Eclipse Marketplace and run install from Neon as well, but the workspace I was using was originally Mars. was (Author: wrestang): Docker Tooling was installed from the Eclipse Marketplace. Installed Software shows Docker Tooling 1.2.0. When looking at Plug-ins, I can actually see that version 2.0.0 was also installed. To be more precise, only the Docker Core Plugin 2.0.0 was installed, the UI Plug-in, Tooling Documentation are at 1.2.0, and the 1.2.0 core plugin was also installed. So, perhaps this is really an issue with installation from the Eclipse Marketplace and having started on Eclipse Mars, once an update is run, it is actually 2.0.0, and everything is happier. > Registry Account Unavailable In Preferences > ------------------------------------------- > > Key: ERT-323 > URL: https://issues.jboss.org/browse/ERT-323 > Project: Eclipse Release Train > Issue Type: Bug > Components: Linux Tools > Affects Versions: Mars.2 (4.5), Neon (4.6) > Environment: Windows 7 Enterprise 64-bit > 64-bit Eclipse > Reporter: Trevor Trevor > Attachments: no_registry_account.png > > > According to the [user guide|https://wiki.eclipse.org/Linux_Tools_Project/Docker_Tooling/User_Guide] "By default, the Docker Hub registry will be used, however, a user may specify an additional private registry if desired. Additional registries are added using Windows -> Preferences -> Docker -> Registry Accounts." > However, the only things available under Docker are "Docker Machine," and "Logging"; "Registry Accounts" is not present. I have observed this on both Eclipse Neon and Mars, and on a different Windows 7 machine. The plugin does work to show containers and images, but this prevents me from being able to connect to private repository on my network. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 June 2016