June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22617) Integrate DockViz in to JBoss docker Tools

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22617?page=com.atlassian.jira.plugi... ] Mustafa Musaji reassigned JBIDE-22617: -------------------------------------- Assignee: Xavier Coulon > Integrate DockViz in to JBoss docker Tools > ------------------------------------------ > > Key: JBIDE-22617 > URL: https://issues.jboss.org/browse/JBIDE-22617 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker > Affects Versions: 4.4.0.Alpha2 > Reporter: Mustafa Musaji > Assignee: Xavier Coulon > Priority: Optional > > DockVIz is a tool used to provide a way to view docker information on a system in a number of ways, one of which is a tree like structure to be able to visualise docker layers. > This would be a nice thing to include in our docker toolset. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22617) Integrate DockViz in to JBoss docker Tools

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22617?page=com.atlassian.jira.plugi... ] Mustafa Musaji commented on JBIDE-22617: ---------------------------------------- See https://github.com/justone/dockviz for more information > Integrate DockViz in to JBoss docker Tools > ------------------------------------------ > > Key: JBIDE-22617 > URL: https://issues.jboss.org/browse/JBIDE-22617 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker > Affects Versions: 4.4.0.Alpha2 > Reporter: Mustafa Musaji > Assignee: Xavier Coulon > Priority: Optional > > DockVIz is a tool used to provide a way to view docker information on a system in a number of ways, one of which is a tree like structure to be able to visualise docker layers. > This would be a nice thing to include in our docker toolset. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22617) Integrate DockViz in to JBoss docker Tools

by Mustafa Musaji (JIRA)

Mustafa Musaji created JBIDE-22617: -------------------------------------- Summary: Integrate DockViz in to JBoss docker Tools Key: JBIDE-22617 URL: https://issues.jboss.org/browse/JBIDE-22617 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: docker Affects Versions: 4.4.0.Alpha2 Reporter: Mustafa Musaji Priority: Optional DockVIz is a tool used to provide a way to view docker information on a system in a number of ways, one of which is a tree like structure to be able to visualise docker layers. This would be a nice thing to include in our docker toolset. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22613) When a connection is configured with a stored token, switching back with basic will fail if token is invalid

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22613?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22613: ------------------------------- Story Points: 2 > When a connection is configured with a stored token, switching back with basic will fail if token is invalid > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-22613 > URL: https://issues.jboss.org/browse/JBIDE-22613 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Fix For: 4.4.1.S117 > > > If an Openshift is configured with a OAuth and a stored token, if you want to switch back to basic, the connection will fail because the connection is still made using Oauth -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22613) When a connection is configured with a stored token, switching back with basic will fail if token is invalid

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22613?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22613: ------------------------------- Fix Version/s: 4.4.1.S117 (was: 4.4.x) > When a connection is configured with a stored token, switching back with basic will fail if token is invalid > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-22613 > URL: https://issues.jboss.org/browse/JBIDE-22613 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Fix For: 4.4.1.S117 > > > If an Openshift is configured with a OAuth and a stored token, if you want to switch back to basic, the connection will fail because the connection is still made using Oauth -- 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 Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBDS-3953?page=com.atlassian.jira.plugin.... ] Snjezana Peco commented on JBDS-3953: ------------------------------------- The following is a workaround: export SWT_GTK3=0 ./jbdevstudio -vmargs -Dorg.eclipse.swt.browser.DefaultType=mozilla It is also recommended to use GTK2 for JBDS 9.x/Eclipse Mars due to the issue described in https://issues.jboss.org/browse/JBIDE-21038 JBDS 10.0.0 works properly without any workarounds. > 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] (JBIDE-20491) "incompatibleImprovements" setting should be set

by Daniel Dekany (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20491?page=com.atlassian.jira.plugi... ] Daniel Dekany commented on JBIDE-20491: --------------------------------------- For the FreemarkerTestUtils issue, see: https://github.com/jbosstools/jbosstools-freemarker/pull/60 > "incompatibleImprovements" setting should be set > ------------------------------------------------ > > Key: JBIDE-20491 > URL: https://issues.jboss.org/browse/JBIDE-20491 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: freemarker > Reporter: Daniel Dekany > Assignee: Denis Golovin > Fix For: 4.4.1.S116 > > > Where the {{freemarker.template.Configuration}} is created, the {{incompatibleImprovements}} setting shouldn't be left on its default, 2.3.0. It should be set to {{Configuration.getVersion()}} (like {{new Configuration(Configuration.getVersion())}}, or with {{config.setIncompatibleImprovements(Configuration.getVersion())}}). > Why: The plugin doesn't execute the templates, just parses them. As of 2.3.24, all the "incompatible" fixes that affect the parser (not the execution) just makes it stricter by eliminating legacy parser glitches that let through things that are pretty much always just user oversights. Also when 2.3.24 is out, the new {{ftlh}} and {{ftlx}} file extensions, which affect parsing, will only have effect with {{incompatibleImprovements}} 2.3.24. -- 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 Donato Marrazzo (JIRA)

[ https://issues.jboss.org/browse/JBDS-3953?page=com.atlassian.jira.plugin.... ] Donato Marrazzo commented on JBDS-3953: --------------------------------------- [~akurtako] I'm not sure if I understood well, should I: * use mozilla as browser {code} -Dorg.eclipse.swt.browser.DefaultType=mozilla -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib64/firefox {code} * remove all the plugins from firefox? > 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] (JBIDE-22612) Explorer: OpenShift 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 updated JBIDE-22612: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/1230, https://github.com/jbosstools/jbosstools-openshift/pull/1232 (was: https://github.com/jbosstools/jbosstools-openshift/pull/1230) > Explorer: OpenShift 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: Bug > Components: openshift > Affects Versions: 4.4.1.S116 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Labels: explorer, openshift_v2, openshift_v3 > Fix For: 4.4.1.S116 > > > 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] (JBDS-3891) Devstudio BYOE install "Committing the provisioning operation" takes too long

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3891?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3891: ---------------------------------- well, then it's all p2 completing the install & generating metadata, etc. You could try reporting this upstream at Eclipse to see if it's a known performance issue. > Devstudio BYOE install "Committing the provisioning operation" takes too long > ----------------------------------------------------------------------------- > > Key: JBDS-3891 > URL: https://issues.jboss.org/browse/JBDS-3891 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: updatesite > Affects Versions: 10.0.0.Alpha1 > Reporter: Jan Richter > Fix For: 10.x > > > Installing nightly devstudio to Eclipse M7 using the BYOE feature - everything goes well until the process gets stuck on "Committing the provisioning operation" for a few minutes. > Looks to be a similar problem to JBDS-3890. -- 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