June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22382) Use different icons for EAP server and Red Hat Central

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22382?page=com.atlassian.jira.plugi... ] Radim Hopp updated JBIDE-22382: ------------------------------- Fix Version/s: 4.4.x (was: 4.4.1.Alpha1) > Use different icons for EAP server and Red Hat Central > ------------------------------------------------------ > > Key: JBIDE-22382 > URL: https://issues.jboss.org/browse/JBIDE-22382 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central, server > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Minor > Labels: respin-a > Fix For: 4.4.x > > Attachments: central-rhd-icon.png > > > If there is an EAP server present in Servers view, workbench tool bar contains 2 same icons - Select a default server icon is same as Red Hat Central icon. We should make this explicitly different. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22382) Use different icons for EAP server and Red Hat Central

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22382?page=com.atlassian.jira.plugi... ] Radim Hopp updated JBIDE-22382: ------------------------------- Fix Version/s: 4.4.1.Alpha1 (was: 4.4.0.Final) > Use different icons for EAP server and Red Hat Central > ------------------------------------------------------ > > Key: JBIDE-22382 > URL: https://issues.jboss.org/browse/JBIDE-22382 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central, server > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Minor > Labels: respin-a > Fix For: 4.4.x > > Attachments: central-rhd-icon.png > > > If there is an EAP server present in Servers view, workbench tool bar contains 2 same icons - Select a default server icon is same as Red Hat Central icon. We should make this explicitly different. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22604) CDK server adapter stuck at starting

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22604?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22604: --------------------------------------- So CDK 2.1.RC5 main Vagrantfile (components/rhel/rhel-ose/Vagrantfile) is now confirmed to work in devstudio on Mac (by me), Windows (by Jan), Fedora (by Ondra?). All looks good. BTW, there is one workaround now to get sshfs setup working with devstudio: 1. Start CDK with sshfs setup from CLI: {code} cd components/rhel/misc/shared_folder/rhel-ose vagrant up {code} 2. Set up CDK in devstudio and start it Devstudio will notice it's already running and so it will mark it as Started immediately, thus circumventing the whole startup which would fail in this case. You can then use the cdk environment as normally - openshift connection and docker connection will both work normally. > CDK server adapter stuck at starting > ------------------------------------ > > Key: JBIDE-22604 > URL: https://issues.jboss.org/browse/JBIDE-22604 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 4.4.0.Final > Environment: development-suite-1.0.0-GA-20160615-188-bundle-installer.exe > devstudio 10.0.0.GA-a > CDK 2.1.RC3 > Reporter: Jan Richter > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.0.Final > > > I have installed the development suite using the all-in-1 installer (on 3 different windows machines now). Every time I try to start CDK using the server adapter it gets stuck on 'starting'. > In fact the CDK does start up, openshift is running, but no connection is created + the server adapter is marked as starting and the job (starting CDK) is spinning until it hits the timeout. > Strange thing is - stopping the job/server adapter at this point will first create the desired openshift connection and then CDK wil stop. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22596) Impossible to connect to OpenShift when landrush is enabled (instead of xip.io)

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22596?page=com.atlassian.jira.plugi... ] Marián Labuda edited comment on JBIDE-22596 at 6/17/16 6:11 AM: ---------------------------------------------------------------- Validation is still working, somehow. When I am trying to create a new connection and fill in all details (e.g. select OS 3, use server "https://console.engint.openshift.com" and OAuth with custom string as a token) and then I fill in registry URL to some random string, not in compliance with validator, there is an validation error in connection wizard header. Attached screencast from Andre to see how it is reproducible: https://www.youtube.com/watch?v=qiKBIRDqkKw was (Author: mlabuda): Validation is still working, somehow. When I am trying to create a new connection and fill in all details (e.g. select OS 3, use server "https://console.engint.openshift.com" and OAuth with custom string as a token) and then I fill in registry URL to some random string, not in compliance with validator, there is an validation error in connection wizard header. > Impossible to connect to OpenShift when landrush is enabled (instead of xip.io) > ------------------------------------------------------------------------------- > > Key: JBIDE-22596 > URL: https://issues.jboss.org/browse/JBIDE-22596 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Blocker > Labels: respin-b > Fix For: 4.4.0.Final > > > When landrush is enabled on the CDK, the Docker registry url is https://hub.openshift.openshift.cdk, it's stored in the OpenShift connection properties when launching the CDK server adapter. > However, URL validation fails on that url, thus preventing the Connection wizard to finish, because *.cdk urls are not valid. Indeed cdk is not a known/valid TLD, according to Apache's commons UrlValidator -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3953) JBoss Studio Developer crash at startup on Fedora 24

by Alexander Kurtakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3953?page=com.atlassian.jira.plugin.... ] Alexander Kurtakov commented on JBDS-3953: ------------------------------------------ I would let someone else investigate Red Hat Central with Webkit 2 - must be done as there as this is the only viable solution that doesn't require uninstalling Browser plugins and quite probably issue with Red Hat Central itself not tested with webkit 2 at all yet. Now, in order to get things working for you (both red hat central working and no crashes) please go and uninstall browser plugins(Flash, Google Talk, Bluejeans, anything else) until you find the offending plugin. > JBoss Studio Developer crash at startup on Fedora 24 > ---------------------------------------------------- > > Key: JBDS-3953 > URL: https://issues.jboss.org/browse/JBDS-3953 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Affects Versions: 9.1.0.GA > Environment: Fedora 24 > openjdk full version "1.8.0_92-b14" > Reporter: Donato Marrazzo > Assignee: Snjezana Peco > Priority: Critical > Fix For: 10.x > > Attachments: hs_err_pid12689.log, hs_err_pid3836.log.zip, Selection_003.png > > > After installation, as I launch JBS, it just display the eclipse workbench for few second that it crash. > Despite the console message, no core dump is generated. > This is the cmd line output: > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in [bundleresource://1072.fwk923366543:1/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in [bundleresource://1072.fwk923366543:2/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. > SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder] > 14:09:55.604 [Worker-2] DEBUG o.e.m.c.i.p.r.ProjectRegistryRefreshJob - Queued refresh request: [/RemoteSystemsTempFiles/pom.xml] > openjdk version "1.8.0_92" > OpenJDK Runtime Environment (build 1.8.0_92-b14) > OpenJDK 64-Bit Server VM (build 25.92-b14, mixed mode) > 14:09:57.115 [Worker-14] DEBUG o.e.a.i.i.DefaultLocalRepositoryProvider - Using manager EnhancedLocalRepositoryManager with priority 10.0 for /home/donato/.m2/repository > 14:09:57.142 [Worker-14] DEBUG o.e.a.i.i.DefaultLocalRepositoryProvider - Using manager EnhancedLocalRepositoryManager with priority 10.0 for /home/donato/.m2/repository > 14:09:57.143 [Worker-14] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshing: [L/RemoteSystemsTempFiles/pom.xml] > 14:09:57.156 [Worker-14] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshed: [L/RemoteSystemsTempFiles/pom.xml] > # > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x00007f521a6d7bfe, pid=12689, tid=0x00007f52cf5a3700 > # > # JRE version: OpenJDK Runtime Environment (8.0_92-b14) (build 1.8.0_92-b14) > # Java VM: OpenJDK 64-Bit Server VM (25.92-b14 mixed mode linux-amd64 compressed oops) > # Problematic frame: > # C [libjavascriptcoregtk-3.0.so.0+0x4d4bfe] JSC::VM::throwException(JSC::ExecState*, JSC::JSValue)+0x236e > # > # Core dump written. Default location: /home/donato/core or core.12689 > # > # An error report file with more information is saved as: > # /home/donato/hs_err_pid12689.log > # > # If you would like to submit a bug report, please visit: > # http://bugreport.java.com/bugreport/crash.jsp > # The crash happened outside the Java Virtual Machine in native code. > # See problematic frame for where to report the bug. > # -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3923) Installer: replace browser tests with UI tests

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3923?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-3923: ------------------------------ Fix Version/s: 10.0.1.Alpha1 > Installer: replace browser tests with UI tests > ---------------------------------------------- > > Key: JBDS-3923 > URL: https://issues.jboss.org/browse/JBDS-3923 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.0.0.Alpha2 > Reporter: Pavol Pitonak > Assignee: Jan Richter > Fix For: 10.0.1.Alpha1 > > > Remove browser tests (tests for Angular directives running using Karma) and create new UI tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22612) Explorer: OpenShift v3 connections are missing from the explorer on startup

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22612?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-22612: ---------------------------------------- Assignee: Andre Dietisheim > Explorer: OpenShift v3 connections are missing from the explorer on startup > --------------------------------------------------------------------------- > > Key: JBIDE-22612 > URL: https://issues.jboss.org/browse/JBIDE-22612 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.Alpha1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Labels: explorer, openshift_v3 > Fix For: 4.4.1.Alpha1 > > > After applying the fix for JBIDE-21828, it appears that, on workspace restart, the OpenShift 3 connections are missing from the OpenShift Explorer. > This is caused by the OpenShift 3 core plugin not being started when the OpenShiftExplorerContentProvider is called. As a consequence, no connections are loaded. > Before JBIDE-21828, [getExplorerElements|https://github.com/jbosstools/jbosstools-openshift/co...] would return all the OpenShift3 connections. With the new code, the UI Model is expected to be already loaded -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22459) Figure out impact of adding EAP 7 to DCP and what changes DCP has that might affect Central

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22459?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-22459. ------------------------------ Verified in Devstudio 10.0.0.GA (B33). Closing. > Figure out impact of adding EAP 7 to DCP and what changes DCP has that might affect Central > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22459 > URL: https://issues.jboss.org/browse/JBIDE-22459 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.4.0.Final > > > ~1 year ago we made Central use DCP for querying the quickstart list to let users start easily with the examples/quickstrats. > In the context of EAP 7 coming out there are new quickstarts. > In a perfect world the following have happend: > EAP 7 Quickstarts added to DCP > Central in both devstudio 9 and 10 can see both EAP 6 and EAP 7 quickstarts > What seem to have happened instead is: > if EAP 7 quickstarts are added to DCP EAP 6 quickstarts are no longer available > DCP has changed its format/approach and not sure what the impact of this is > (can devstudio 9 still work ? must devstudio 10 change ? will we ever have multiple version support ?) > This bug is to gather the facts and figure out what we do about them. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22604) CDK server adapter stuck at starting

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22604?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22604: ------------------------------------ 1.1.1 was a tentative fix and it not yet release as it does not fix for Windows and is not fully tested for Linux. So the plan was to remove sshfs mount from default Vagrant file and add a new Vagranfile with sshfs mount in misc folder > CDK server adapter stuck at starting > ------------------------------------ > > Key: JBIDE-22604 > URL: https://issues.jboss.org/browse/JBIDE-22604 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 4.4.0.Final > Environment: development-suite-1.0.0-GA-20160615-188-bundle-installer.exe > devstudio 10.0.0.GA-a > CDK 2.1.RC3 > Reporter: Jan Richter > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.0.Final > > > I have installed the development suite using the all-in-1 installer (on 3 different windows machines now). Every time I try to start CDK using the server adapter it gets stuck on 'starting'. > In fact the CDK does start up, openshift is running, but no connection is created + the server adapter is marked as starting and the job (starting CDK) is spinning until it hits the timeout. > Strange thing is - stopping the job/server adapter at this point will first create the desired openshift connection and then CDK wil stop. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22612) Explorer: OpenShift v3 connections are missing from the explorer on startup

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22612?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22612: ------------------------------------------ IMHO the view should always be the trigger for any loading (and thus plugin activation) to happen. If there's no view, no plugin (neither ui nor core) should get activated nor loaded. Since the org.jboss.tools.openshift.core plugin is set to get activated when one of it's classes is accessed (Bundle-ActivationPolicy: lazy) I suspect the v3 content provider no to access any of the v3 core classes. > Explorer: OpenShift v3 connections are missing from the explorer on startup > --------------------------------------------------------------------------- > > Key: JBIDE-22612 > URL: https://issues.jboss.org/browse/JBIDE-22612 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.Alpha1 > Reporter: Fred Bricon > Labels: explorer, openshift_v3 > Fix For: 4.4.1.Alpha1 > > > After applying the fix for JBIDE-21828, it appears that, on workspace restart, the OpenShift 3 connections are missing from the OpenShift Explorer. > This is caused by the OpenShift 3 core plugin not being started when the OpenShiftExplorerContentProvider is called. As a consequence, no connections are loaded. > Before JBIDE-21828, [getExplorerElements|https://github.com/jbosstools/jbosstools-openshift/co...] would return all the OpenShift3 connections. With the new code, the UI Model is expected to be already loaded -- 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