November 2016 - jbosstools-issues

[JBoss JIRA] (ERT-389) TypeScript debugging [EBZ#487465]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-389?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-389: ---------------------------- Priority: Major (was: Trivial) > TypeScript debugging [EBZ#487465] > --------------------------------- > > Key: ERT-389 > URL: https://issues.jboss.org/browse/ERT-389 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: Debug, bzira > > I'm developping a TypeScript plugins based on JSDT & tsserver https://github.com/angelozerr/typescript.java and it should be very cool if JSDT debugger could debug TypeScript (by using source map). > If you are interested to work together about integration TypeScript (with JSDT), I have created an issue at https://github.com/angelozerr/typescript.java/issues/2. > Please note that TypEcs support debugging with Eclipse https://github.com/axmor/typecs/tree/master/src/com.axmor.eclipse.typescr... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23148) Properties: Extended properties are not displayed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23148?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23148: ------------------------------------- Fix Version/s: 4.4.2.Final (was: 4.4.x) > Properties: Extended properties are not displayed > ------------------------------------------------- > > Key: JBIDE-23148 > URL: https://issues.jboss.org/browse/JBIDE-23148 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Jeff MAURY > Assignee: Viacheslav Kabanovich > Labels: openshift, openshift_v3, properties > Fix For: 4.4.2.Final > > > When an OS3 connection is displayed in the property view, the extended properties are not displayed -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23148) Properties: Extended properties are not displayed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23148?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23148: ------------------------------------------ merged into master. > Properties: Extended properties are not displayed > ------------------------------------------------- > > Key: JBIDE-23148 > URL: https://issues.jboss.org/browse/JBIDE-23148 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Jeff MAURY > Assignee: Viacheslav Kabanovich > Labels: openshift, openshift_v3, properties > Fix For: 4.4.2.Final > > > When an OS3 connection is displayed in the property view, the extended properties are not displayed -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4187) oc client tool is not added to PATH after installation on macOS

by Denis Golovin (JIRA)

Denis Golovin created JBDS-4187: ----------------------------------- Summary: oc client tool is not added to PATH after installation on macOS Key: JBDS-4187 URL: https://issues.jboss.org/browse/JBDS-4187 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 10.2.0.GA Environment: macOS Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 10.2.0.GA -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4186) oc client tool has no execution permission after install on macOS

by Denis Golovin (JIRA)

Denis Golovin created JBDS-4186: ----------------------------------- Summary: oc client tool has no execution permission after install on macOS Key: JBDS-4186 URL: https://issues.jboss.org/browse/JBDS-4186 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 10.2.0.GA Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 10.2.0.GA After installation on macOS devstudio cannot get pod logs, because it cannot execute oc from cdk/bin folder. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4185) Publish windows and macOS builds to the same location

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4185?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-4185: ----------------------------------- Assignee: Jan Richter (was: Denis Golovin) [~jrichter1] could you look at it? > Publish windows and macOS builds to the same location > ----------------------------------------------------- > > Key: JBDS-4185 > URL: https://issues.jboss.org/browse/JBDS-4185 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.2.0.GA > Reporter: Denis Golovin > Assignee: Jan Richter > Fix For: 10.2.0.GA > > > Currently we have two jenkins CI projects building DevSuite Installer: > 1. Windows build; > 2. macOS build. > (1) is publishing bits to http://cdk-builds.usersys.redhat.com/builds/nightly/devsuite/; > (2) is not publishing them at all; > We need to trigger both when something released into git repository and then publish both builds into the same folder on http://cdk-builds.usersys.redhat.com/builds/nightly/devsuite/. > Possible solution is introducing third build that would generate folder name, create that folder in http://cdk-builds.usersys.redhat.com/builds/nightly/devsuite/ and then would trigger (1) and (2) passing them folder name as a parameter. Builds would publish bits to that location after build is finished. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4185) Publish windows and macOS builds to the same location

by Denis Golovin (JIRA)

Denis Golovin created JBDS-4185: ----------------------------------- Summary: Publish windows and macOS builds to the same location Key: JBDS-4185 URL: https://issues.jboss.org/browse/JBDS-4185 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 10.2.0.GA Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 10.2.0.GA Currently we have two jenkins CI projects building DevSuite Installer: 1. Windows build; 2. macOS build. (1) is publishing bits to http://cdk-builds.usersys.redhat.com/builds/nightly/devsuite/; (2) is not publishing them at all; We need to trigger both when something released into git repository and then publish both builds into the same folder on http://cdk-builds.usersys.redhat.com/builds/nightly/devsuite/. Possible solution is introducing third build that would generate folder name, create that folder in http://cdk-builds.usersys.redhat.com/builds/nightly/devsuite/ and then would trigger (1) and (2) passing them folder name as a parameter. Builds would publish bits to that location after build is finished. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4179) DevStudio installer uses console installation instead of wizard

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-4179?page=com.atlassian.jira.plugin.... ] Misha Ali commented on JBDS-4179: --------------------------------- [~supriya.bharadwaj], see above. > DevStudio installer uses console installation instead of wizard > --------------------------------------------------------------- > > Key: JBDS-4179 > URL: https://issues.jboss.org/browse/JBDS-4179 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: documentation, installer, upstream > Affects Versions: 10.2.0.GA > Environment: openjdk version "1.8.0_102" > OpenJDK Runtime Environment (build 1.8.0_102-b14) > Reporter: Marián Labuda > Assignee: Denis Golovin > Fix For: 10.x > > > I tried to install latest DevStudio (devstudio-10.2.0.GA-v20161116-0039-B6472-installer-standalone.jar) but when I run installation as usual, I get console installation - at first whole license text and prompt to 1) Accept, 2) Reject, 3) Redisplay. After that installation unpack files to home and I am not able to select destination. > This happens with older version of openjdk8. With latest available openjdk for fedora (1.8.0_111) it works. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4180) ClassNotFoundException thrown on devstudio start up

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-4180?page=com.atlassian.jira.plugin.... ] Rob Stryker commented on JBDS-4180: ----------------------------------- I'm having trouble figuring out where to get that specific build. Where can I find specific builds of openjdk? I've been googling for like 90 minutes. I'm a failure. > ClassNotFoundException thrown on devstudio start up > --------------------------------------------------- > > Key: JBDS-4180 > URL: https://issues.jboss.org/browse/JBDS-4180 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: foundation, upstream > Affects Versions: 10.2.0.GA > Environment: Fedora 24, > openjdk version "1.8.0_102" > OpenJDK Runtime Environment (build 1.8.0_102-b14) > Reporter: Marián Labuda > Assignee: Rob Stryker > Fix For: 10.x > > > When starting latest DevStudio 10.2.0.GA (build ID GA-v20161116-0039-B6472) I get following error in console output > {code} > SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder] > Noop constructor > java.lang.ClassNotFoundException: sun.jvmstat.monitor.MonitoredHost > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at org.eclipse.osgi.internal.framework.ContextFinder.loadClass(ContextFinder.java:132) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredHost(Tools.java:513) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.validateClassPathAndLibraryPath(Tools.java:365) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.reset(Tools.java:115) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.<init>(Tools.java:82) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getInstance(Tools.java:73) > at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getActiveProcessIds(ToolsCore.java:179) > at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:100) > at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > java.lang.ClassNotFoundException: sun.jvmstat.monitor.MonitoredHost > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at org.eclipse.osgi.internal.framework.ContextFinder.loadClass(ContextFinder.java:132) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredHost(Tools.java:513) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeActiveVms(Tools.java:525) > at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getActiveProcessIds(ToolsCore.java:179) > at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:100) > at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > {code} > problem is with openjdk version. With the lates 1.8.0_111 it works. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4184) Can't update/install plugins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4184?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4184: ----------------------------- Fix Version/s: 10.2.0.GA > Can't update/install plugins > ---------------------------- > > Key: JBDS-4184 > URL: https://issues.jboss.org/browse/JBDS-4184 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Affects Versions: 10.2.0.GA > Environment: RHEL 7 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 10.2.0.GA > > Attachments: rh-eclipse46-devstudio10.2.log.20161113.1010_update.txt, rh-eclipse46-devstudio10.2.log.20161116.1305_update_2.txt > > > I tried "Check for Updates" in DevStudio 20161116.1305 and 20161113.1010. I used this update site: > [1] https://devstudio.redhat.com/10.0/snapshots/updates/ > Eclipse was not able to detect any updates (I got "No updates were found" message). > Then I tried to install plugins using "Install new software". > Install new software->select Bring Your Own Eclipse->next->restart > Eclipse didn't detect any problems or conflicts during installation but after restart I got a lot of errors and eclipse didn't start. > [^rh-eclipse46-devstudio10.2.log.20161116.1305_update_2.txt] > [^rh-eclipse46-devstudio10.2.log.20161113.1010_update.txt] > I also noticed there isn't update site [1] by default after installation. I had to add it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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