October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22762) JMX remote call results (and others) cannot be copied using Cmd+C

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22762?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22762: -------------------------------- Fix Version/s: 4.4.2.AM3 > JMX remote call results (and others) cannot be copied using Cmd+C > ------------------------------------------------------------------ > > Key: JBIDE-22762 > URL: https://issues.jboss.org/browse/JBIDE-22762 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.4.1.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.2.AM3 > > > I was verifying JBIDE-22549 which was supposed to add support for Ctrl+C in JMX remote call results. This doesn't work for me on Mac. Right-click -> Copy does work though. > What I did was: > 1. Start EAP 7 > 2. Connect in JMX Navigator > 3. Go to MBeans -> jboss.as -> naming > 4. Double click the mbean > 5. Execute jndiView > In the result window, I am not able to copy anything using Cmd+C, but I can copy using right-click -> Copy. > I asked [~rhopp] to try this for me on Linux. But he got stuck on failed jmx connection of his local EAP 7 server (reported here: JBIDE-22761). And then I tried a similar thing in the Properties view and it turns out that I can't copy there either. Then I asked Radim to check that and he confirmed he cannot copy from Properties view using Ctrl+C on linux. > Then I tried some more and noticed that in some occasions I can do that: > For example if I select the active JMX connection in JMX Navigator, go to Properties view, expand Memory and select a row, I can copy with Cmd+C. But if I select an MBean and then click a row in the Properties view, I cannot copy with Cmd+C. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22762) JMX remote call results (and others) cannot be copied using Cmd+C

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22762?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-22762: ----------------------------------- Assignee: Rob Stryker > JMX remote call results (and others) cannot be copied using Cmd+C > ------------------------------------------------------------------ > > Key: JBIDE-22762 > URL: https://issues.jboss.org/browse/JBIDE-22762 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.4.1.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.2.AM3 > > > I was verifying JBIDE-22549 which was supposed to add support for Ctrl+C in JMX remote call results. This doesn't work for me on Mac. Right-click -> Copy does work though. > What I did was: > 1. Start EAP 7 > 2. Connect in JMX Navigator > 3. Go to MBeans -> jboss.as -> naming > 4. Double click the mbean > 5. Execute jndiView > In the result window, I am not able to copy anything using Cmd+C, but I can copy using right-click -> Copy. > I asked [~rhopp] to try this for me on Linux. But he got stuck on failed jmx connection of his local EAP 7 server (reported here: JBIDE-22761). And then I tried a similar thing in the Properties view and it turns out that I can't copy there either. Then I asked Radim to check that and he confirmed he cannot copy from Properties view using Ctrl+C on linux. > Then I tried some more and noticed that in some occasions I can do that: > For example if I select the active JMX connection in JMX Navigator, go to Properties view, expand Memory and select a row, I can copy with Cmd+C. But if I select an MBean and then click a row in the Properties view, I cannot copy with Cmd+C. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22762) JMX remote call results (and others) cannot be copied using Cmd+C

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22762?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22762: ------------------------------------- > In the result window, I am not able to copy anything using Cmd+C, but I can copy using right-click -> Copy. I am not able to replicate this. ctrl+c works as expected. But a bit of googling shows I should also check for SWT.COMMAND instead of just SWT.CTRL, so I'll make a patch to do that. I'm making a commit to fix only the result dialog. You'll need to open a new jira for the properties pages, and they will be low priority as they are not our primary use case for this. > JMX remote call results (and others) cannot be copied using Cmd+C > ------------------------------------------------------------------ > > Key: JBIDE-22762 > URL: https://issues.jboss.org/browse/JBIDE-22762 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.4.1.AM2 > Reporter: Martin Malina > > I was verifying JBIDE-22549 which was supposed to add support for Ctrl+C in JMX remote call results. This doesn't work for me on Mac. Right-click -> Copy does work though. > What I did was: > 1. Start EAP 7 > 2. Connect in JMX Navigator > 3. Go to MBeans -> jboss.as -> naming > 4. Double click the mbean > 5. Execute jndiView > In the result window, I am not able to copy anything using Cmd+C, but I can copy using right-click -> Copy. > I asked [~rhopp] to try this for me on Linux. But he got stuck on failed jmx connection of his local EAP 7 server (reported here: JBIDE-22761). And then I tried a similar thing in the Properties view and it turns out that I can't copy there either. Then I asked Radim to check that and he confirmed he cannot copy from Properties view using Ctrl+C on linux. > Then I tried some more and noticed that in some occasions I can do that: > For example if I select the active JMX connection in JMX Navigator, go to Properties view, expand Memory and select a row, I can copy with Cmd+C. But if I select an MBean and then click a row in the Properties view, I cannot copy with Cmd+C. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23429) Jolokia JMX connection

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23429?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-23429: ----------------------------------- Assignee: Rob Stryker > Jolokia JMX connection > ---------------------- > > Key: JBIDE-23429 > URL: https://issues.jboss.org/browse/JBIDE-23429 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Affects Versions: 4.4.2.AM2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.2.AM3 > > > A jolokia JMX connection would be useful for some users, and could also be used to connect to JMX for an EAP behind openshift / cdk. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23428) JMX connection for EAP behind OpenShift / CDK

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23428?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-23428: ----------------------------------- Assignee: Rob Stryker > JMX connection for EAP behind OpenShift / CDK > --------------------------------------------- > > Key: JBIDE-23428 > URL: https://issues.jboss.org/browse/JBIDE-23428 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk, jmx, openshift > Affects Versions: 4.4.2.AM2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.2.AM3 > > > In order to allow garbage collection for HCR behind openshift, we need a JMX connection capable of doing it. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23135) Verify every EAP 7.1 devel/candidate works with eap7x Server adapter

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23135?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23135: ------------------------------------- Just tested DR7 and it seems to work for shutdown, deploy, stop deployment, remove deployment, in local + management profile. > Verify every EAP 7.1 devel/candidate works with eap7x Server adapter > -------------------------------------------------------------------- > > Key: JBIDE-23135 > URL: https://issues.jboss.org/browse/JBIDE-23135 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.2.AM3 > > -- This message was sent by Atlassian JIRA (v7.2.2#72004)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23423) test failures in base for org.jboss.tools.runtime.test.RuntimeDetectionAllTests

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23423?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-23423. --------------------------------- Resolution: Done deleted unnecessary traces. As far as I know there's also another exception in InvalidHandler, and this is intended. > test failures in base for org.jboss.tools.runtime.test.RuntimeDetectionAllTests > ------------------------------------------------------------------------------- > > Key: JBIDE-23423 > URL: https://issues.jboss.org/browse/JBIDE-23423 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Rob Stryker > Fix For: 4.4.2.AM3 > > Attachments: base-tests-failure-full-log.txt, base-tests-failure.txt > > > See attached logs. Jenkins is not reporting these failures as failing tests, so the job is blue and the test results are 100%. This is bad. :( -- This message was sent by Atlassian JIRA (v7.2.2#72004)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22326) Enable JMX Connections Over "remoting-jmx"

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22326?page=com.atlassian.jira.plugi... ] Rob Stryker closed JBIDE-22326. ------------------------------- Resolution: Rejected This issue is poorly defined. We also have a jolokia as the proof-of-concept method for connecting to JMX for eap behind openshift. > Enable JMX Connections Over "remoting-jmx" > ------------------------------------------ > > Key: JBIDE-22326 > URL: https://issues.jboss.org/browse/JBIDE-22326 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Reporter: Thomas Mäder > Assignee: Rob Stryker > Fix For: 4.4.2.AM3 > > > Need to add "remoting-jmx" library and support that kind of connection for jmx -- This message was sent by Atlassian JIRA (v7.2.2#72004)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4133) An internal error occurred during: "JAX-RS Metamodel build" - java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4133?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4133: ---------------------------------- Thanks for confirming what I reported in https://issues.jboss.org/browse/JBDS-4133?focusedCommentId=13313625&page=... [~jeffmaury] ... now we just need a PR. Can you provide one? > An internal error occurred during: "JAX-RS Metamodel build" - java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer > -------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-4133 > URL: https://issues.jboss.org/browse/JBDS-4133 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm, webservices > Affects Versions: 10.2.0.AM2 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 10.2.0.AM3 > > Attachments: lucene3.5corevs.5.4.1analyzers-common.png, lucene3.5corevs.5.4.1queryparser.png > > > I'm getting this problem after running the HTML5 quickstart. I've installed this [1] version of the rpm. > {code} > !ENTRY org.eclipse.core.jobs 4 2 2016-10-26 16:22:07.578 > !MESSAGE An internal error occurred during: "JAX-RS Metamodel build...". > !STACK 0 > java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.<init>(JaxrsMetamodel.java:163) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.create(JaxrsMetamodel.java:278) > at org.jboss.tools.ws.jaxrs.core.metamodel.domain.JaxrsMetamodelLocator.get(JaxrsMetamodelLocator.java:120) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedBuildJob.run(ResourceChangedBuildJob.java:68) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: java.lang.ClassNotFoundException: org.apache.lucene.analysis.standard.StandardAnalyzer cannot be found by org.jboss.tools.ws.jaxrs.core_1.9.2.v20161011-1002 > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:461) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > ... 5 more > {code} > [1] https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_master/20... -- This message was sent by Atlassian JIRA (v7.2.2#72004)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23423) test failures in base for org.jboss.tools.runtime.test.RuntimeDetectionAllTests

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23423?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23423: ------------------------------------- I'm not entirely sure why those are there... I guess I can delete them with no effect, since it seems purely cosmetic and doesn't seem to serve any purpose. > test failures in base for org.jboss.tools.runtime.test.RuntimeDetectionAllTests > ------------------------------------------------------------------------------- > > Key: JBIDE-23423 > URL: https://issues.jboss.org/browse/JBIDE-23423 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Rob Stryker > Fix For: 4.4.2.AM3 > > Attachments: base-tests-failure-full-log.txt, base-tests-failure.txt > > > See attached logs. Jenkins is not reporting these failures as failing tests, so the job is blue and the test results are 100%. This is bad. :( -- This message was sent by Atlassian JIRA (v7.2.2#72004)

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 October 2016