November 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23516) Server Adapter: DC of debugged java application use nodejs debugging env var

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23516?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23516: ------------------------------------------ [~mlabuda] DEV_MODE is not nodejs specific. DEV_MODE is an env var that is intendend to be used across all openshift images, see CLOUD-243. Reading you there seems to be an inconsistency in the latest eap image? > Server Adapter: DC of debugged java application use nodejs debugging env var > ---------------------------------------------------------------------------- > > Key: JBIDE-23516 > URL: https://issues.jboss.org/browse/JBIDE-23516 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Marián Labuda > Labels: debugging, openshift_v3, server_adapter > > When debugging an EAP application on OpenShift, deployment config is modified. In nodejs debugging there is added an environment variable DEV_MODE. For java debugging it is not necessary but I found it in deployment config. I compared deployment config before starting debugging and after and it was added by tooling. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23492) "What's New" Left menu is not scrollable

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23492?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-23492: ---------------------------------- Fix Version/s: 4.4.x > "What's New" Left menu is not scrollable > ---------------------------------------- > > Key: JBIDE-23492 > URL: https://issues.jboss.org/browse/JBIDE-23492 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.4.1.Final > Reporter: Josef Kopriva > Priority: Minor > Fix For: 4.4.x > > Attachments: whatsnew-leftmenu.png > > > Left menu on page "What's New" is always on top, so when release (e.g. 4.3.0.Final) have more subitems I cannot see or scroll to release 4.1.2.Final, this item is accessible if I click on release with just a few items. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23492) "What's New" Left menu is not scrollable

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23492?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-23492: ---------------------------------- Affects Version/s: 4.4.1.Final > "What's New" Left menu is not scrollable > ---------------------------------------- > > Key: JBIDE-23492 > URL: https://issues.jboss.org/browse/JBIDE-23492 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.4.1.Final > Reporter: Josef Kopriva > Priority: Minor > Fix For: 4.4.x > > Attachments: whatsnew-leftmenu.png > > > Left menu on page "What's New" is always on top, so when release (e.g. 4.3.0.Final) have more subitems I cannot see or scroll to release 4.1.2.Final, this item is accessible if I click on release with just a few items. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23492) "What's New" Left menu is not scrollable

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23492?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-23492: ------------------------------------- Assignee: Xavier Coulon > "What's New" Left menu is not scrollable > ---------------------------------------- > > Key: JBIDE-23492 > URL: https://issues.jboss.org/browse/JBIDE-23492 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.4.1.Final > Reporter: Josef Kopriva > Assignee: Xavier Coulon > Priority: Minor > Fix For: 4.4.x > > Attachments: whatsnew-leftmenu.png > > > Left menu on page "What's New" is always on top, so when release (e.g. 4.3.0.Final) have more subitems I cannot see or scroll to release 4.1.2.Final, this item is accessible if I click on release with just a few items. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22375) Improve HCR OpenShift

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22375?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22375: --------------------------------------- Need more info to verify that it is working. What has been done there? I see in description that previously change of a method signature resulted into failure. Should it be fixed now? > Improve HCR OpenShift > --------------------- > > Key: JBIDE-22375 > URL: https://issues.jboss.org/browse/JBIDE-22375 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: jmx, openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.2.Final > > > When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will : > - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync > - will always fail if a method signature changed, the debugger saying JDK is out of sync > Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server) > This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23516) Server Adapter: DC of debugged java application use nodejs debugging env var

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23516?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-23516: ---------------------------------- Labels: debugging openshift_v3 server_adapter (was: ) > Server Adapter: DC of debugged java application use nodejs debugging env var > ---------------------------------------------------------------------------- > > Key: JBIDE-23516 > URL: https://issues.jboss.org/browse/JBIDE-23516 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Marián Labuda > Labels: debugging, openshift_v3, server_adapter > > When debugging an EAP application on OpenShift, deployment config is modified. In nodejs debugging there is added an environment variable DEV_MODE. For java debugging it is not necessary but I found it in deployment config. I compared deployment config before starting debugging and after and it was added by tooling. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23512) Properties: Header hidden by another header is not retrievable

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23512?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23512: ------------------------------------------ [~mlabuda] ok, groked. Yes in the table one cannot grab the column any more. Do you know how does it behave in other platforms? I suspect this being specific to GTK. > Properties: Header hidden by another header is not retrievable > -------------------------------------------------------------- > > Key: JBIDE-23512 > URL: https://issues.jboss.org/browse/JBIDE-23512 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Marián Labuda > Priority: Minor > Labels: openshift_v3, properties > Fix For: 4.4.x > > Attachments: out-1.ogv, properties.ogv > > > Table header in Properties for OpenShift 3 resources can be moved/resized. If I resize a header to beginning of another header, the another header is hidden and I cant resize is back or retrieve the second header with its column. See video for more details -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23516) Server Adapter: DC of debugged java application use nodejs debugging env var

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-23516: ------------------------------------- Summary: Server Adapter: DC of debugged java application use nodejs debugging env var Key: JBIDE-23516 URL: https://issues.jboss.org/browse/JBIDE-23516 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.2.Final Reporter: Marián Labuda When debugging an EAP application on OpenShift, deployment config is modified. In nodejs debugging there is added an environment variable DEV_MODE. For java debugging it is not necessary but I found it in deployment config. I compared deployment config before starting debugging and after and it was added by tooling. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22376) Enable JMX when entering Debug mode

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22376?page=com.atlassian.jira.plugi... ] Marián Labuda edited comment on JBIDE-22376 at 11/24/16 5:11 AM: ----------------------------------------------------------------- What has been done there precisely? So i can verify its working as expected. I compared DC of a new application and a deployment config of application in debugging. There is a new port for debug 8787, but what with latest changes to EAP images the jolokia port is 8787 so basically we have 2 same ports with a different name, I don't think it is necessary. Then there are added environment variables: {code} { "name" : "DEBUG_PORT", "value" : "8787" }, { "name" : "DEV_MODE", "value" : "true" }, { "name" : "DEBUG", "value" : "true" } {code} DEV_MOVE env var was added by mistake probably bcs. of nodejs debugging. It is not required for EAP debugging AFAIK. With DEBUG and DEBUG_PORT env vars. I am not sure, should those be there? was (Author: mlabuda): What has been done there precisely? So i can verify its working as expected. I compared DC of a new application and a deployment config of application in debugging. There is a new port for debug 8787, but what with latest changes to EAP images the jolokia port is 8787 so basically we have 2 same ports with a different name, I don't think it is necessary. Then there are added environment variables: {code} }, { "name" : "DEBUG_PORT", "value" : "8787" }, { "name" : "DEV_MODE", "value" : "true" }, { "name" : "DEBUG", "value" : "true" } {code} > Enable JMX when entering Debug mode > ----------------------------------- > > Key: JBIDE-22376 > URL: https://issues.jboss.org/browse/JBIDE-22376 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx, openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Thomas Mäder > Assignee: Rob Stryker > Fix For: 4.4.2.Final, 4.4.3.AM1, 4.5.0.AM1 > > > We need to update the deployment configuration when entering debug mode. It is not entirely clear how to determine that an Openshift Pod has indeed a wildfly/EAP in it and can be reached with remoting-jmx -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23315) Connection wizard: "Advanced >>" Button is cropped

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23315?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23315: ------------------------------------------ I see issues with the PR, see https://github.com/jbosstools/jbosstools-openshift/pull/1374 > Connection wizard: "Advanced >>" Button is cropped > -------------------------------------------------- > > Key: JBIDE-23315 > URL: https://issues.jboss.org/browse/JBIDE-23315 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Priority: Minor > Labels: connection_wizard > Fix For: 4.4.x > > Attachments: 2016-11-23 at 15-04-44.mp4, screenshot-1.png > > -- 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