December 2016 - jbosstools-issues

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22376?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22376: ------------------------------------------ [~mlabuda] yes I can confirm this. You need the server adapter to be in Debug mode and you have to create a structural change (that is not hot code replaceable with default means) so that JMX gets connected. But once you have these 2 conditions met, JMX is connected automatically. Resolving, Re-closing as discussed. > 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 > > > 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)

7 years, 6 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 12/1/16 6:23 AM: ---------------------------------------------------------------- Ok, after further investigation JMX is not enabled by default when entering debug mode on OpenShift Server adapter. It gets connected but it needs few seconds after restarting of a module (prompt shown if HCR incompatible change has been done). If this is intended and it is the issue this JIRA is targeting, please confirm and we can close this one. was (Author: mlabuda): Ok, after further investigation JMX is not enabled by default when entering debug mode on OpenShift Server adapter. It gets connected few seconds after restarting of a module if HCR incompatible change has been done. If this is intended and it is the issue this JIRA is targeting, please confirm and we can close this one. > 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)

7 years, 6 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 commented on JBIDE-22376: --------------------------------------- Ok, after further investigation JMX is not enabled by default when entering debug mode on OpenShift Server adapter. It gets connected few seconds after restarting of a module if HCR incompatible change has been done. If this is intended and it is the issue this JIRA is targeting, please confirm and we can close this one. > 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)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23593) Integration tests global refactoring: org.jboss.tools.ui.bot.ext.test

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23593?page=com.atlassian.jira.plugi... ] Martin Malina edited comment on JBIDE-23593 at 12/1/16 5:59 AM: ---------------------------------------------------------------- Actually, I was incorrect. org.jboss.tools.ui.bot.ext.test really were some tests of org.jboss.tools.ui.bot.ext which is in plugins/. I thought we could just remove both of them. The build still worked, but then I found out that some tests still use bot.ext: {code} $ find . -iname 'manifest.mf' -path '*/META-INF/*'|xargs grep 'ui\.bot\.ext'|sed 's/:.*//'./plugins/org.jboss.tools.jst.ui.bot/META-INF/MANIFEST.MF ./plugins/org.jboss.tools.perf.test.core/META-INF/MANIFEST.MF ./tests/org.jboss.tools.jsf.ui.bot.test/META-INF/MANIFEST.MF ./tests/org.jboss.tools.portlet.ui.bot.test/META-INF/MANIFEST.MF ./tests/org.jboss.tools.runtime.as.ui.bot.test/META-INF/MANIFEST.MF ./tests/org.jboss.tools.seam.ui.bot.test/META-INF/MANIFEST.MF ./tests/org.jboss.tools.ws.ui.bot.test/META-INF/MANIFEST.MF {code} So it's gonna take a bit longer before we're able to get rid of bot.ext. As for bot.ext.test, we discussed it and [~rawagner] had a good point: {quote} Nobody's gonna fix bot.ext (it's deprecated) even if bot.ext.test was to find a problem in it. {quote} So it's not worth bothering with it and it can be removed right now. was (Author: mmalina): Actually, I was incorrect. org.jboss.tools.ui.bot.ext.test really were some tests of org.jboss.tools.ui.bot.ext which is in plugins/. But anyway, let's remove both. PR will follow shortly. > Integration tests global refactoring: org.jboss.tools.ui.bot.ext.test > --------------------------------------------------------------------- > > Key: JBIDE-23593 > URL: https://issues.jboss.org/browse/JBIDE-23593 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: integration-tests > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Labels: integration, integration_tests > Fix For: 4.4.3.AM1 > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.ui.bot.ext.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4211) Change yum repository configuration

by Lukáš Valach (JIRA)

Lukáš Valach created JBDS-4211: ---------------------------------- Summary: Change yum repository configuration Key: JBDS-4211 URL: https://issues.jboss.org/browse/JBDS-4211 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Enhancement Components: rpm Affects Versions: 10.3.0.AM1 Reporter: Lukáš Valach Assignee: Nick Boldt Priority: Optional Fix For: 10.3.0.AM1 I spoke with [~vkadlcik] about yum repository configuration. Václav has proposed to remove these lines from config file: * sslverify=0 Vašek said: _If it mean that user have to install some certification then this fact should be mentioned in documentation._ I removed this parameter and I was still able to install RPM. I didn't have to install any certification, so we can remove this parameter I guess. * gpgcheck=0 GPG check should be enabled (but we have to sign RPM package JBDS-4197) * includepkgs=rh-eclipse* we don't need that * skip_if_unavailable=1 This feature is disabled by default. We haven't reason to change this behaviour. It might seems that we are not able to keep our repository online. It depends on the user if he would like to skip unavailable repositories. We need to update this guide https://devstudio.jboss.com/10.0/snapshots/rpms/10.3.0/x86_64/ and we also need to update install guide (CC:[~supriya.bharadwaj]) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23593) Integration tests global refactoring: org.jboss.tools.ui.bot.ext.test

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23593?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23593: --------------------------------------- Actually, I was incorrect. org.jboss.tools.ui.bot.ext.test really were some tests of org.jboss.tools.ui.bot.ext which is in plugins/. But anyway, let's remove both. PR will follow shortly. > Integration tests global refactoring: org.jboss.tools.ui.bot.ext.test > --------------------------------------------------------------------- > > Key: JBIDE-23593 > URL: https://issues.jboss.org/browse/JBIDE-23593 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: integration-tests > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Labels: integration, integration_tests > Fix For: 4.4.3.AM1 > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.ui.bot.ext.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23603) Server adapter: changes to eap are (published but) not visible unless in debug

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23603?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-23603 at 12/1/16 5:37 AM: ------------------------------------------------------------------- [~rcernich] I would guess that this is related to the devmode that we're having in the eap image for OpenShift. Is this intented? was (Author: adietish): [~rcernich] is this intented? > Server adapter: changes to eap are (published but) not visible unless in debug > ------------------------------------------------------------------------------ > > Key: JBIDE-23603 > URL: https://issues.jboss.org/browse/JBIDE-23603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Andre Dietisheim > Fix For: 4.4.3.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23603) Server adapter: changes to eap are (published but) not visible unless in debug

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23603?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23603: ------------------------------------------ [~rcernich] is this intented? > Server adapter: changes to eap are (published but) not visible unless in debug > ------------------------------------------------------------------------------ > > Key: JBIDE-23603 > URL: https://issues.jboss.org/browse/JBIDE-23603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Andre Dietisheim > Fix For: 4.4.3.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22376?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22376: ------------------------------------------ [~mlabuda] in https://issues.jboss.org/browse/JBIDE-21857?focusedCommentId=13331797&pag... I pasted my steps where I was not connecting JMX manually. I was doing incompatible changes, had the "Hot Code Replace Failed" dialog, which I told to restart the module, and once I checked the adapter again, JMX was connected (See screenshot). As far as I can see JMX is automatically connected once I do structural changes to a class. So imho this issue works. Do I miss something? > 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)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23593) Integration tests global refactoring: org.jboss.tools.ui.bot.ext.test

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23593?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-23593: ------------------------------------ I'm in favor of removing stuff that is not used anymore. This is misleading for newcomers > Integration tests global refactoring: org.jboss.tools.ui.bot.ext.test > --------------------------------------------------------------------- > > Key: JBIDE-23593 > URL: https://issues.jboss.org/browse/JBIDE-23593 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: integration-tests > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Labels: integration, integration_tests > Fix For: 4.4.3.AM1 > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.ui.bot.ext.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2016