September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18259) Refresh MBean section keeps blinking in the status bar

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18259?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-18259: --------------------------------------- [~rob.stryker] if you won't have time to change the behavior right now, as a quick fix we could at least increase the default. [~maxandersen] I saw this with a local server, so I'm not sure why you haven't seen it. > Refresh MBean section keeps blinking in the status bar > ------------------------------------------------------ > > Key: JBIDE-18259 > URL: https://issues.jboss.org/browse/JBIDE-18259 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR2 > > Attachments: refresh-mbean.png > > > When you connect to a local process in the JMX Navigator and then check out some mbeans in the Properties view, there will be a "Refresh MBean section" message blinking in the status bar at the bottom of Eclipse every second or so. > Screenshot: > !refresh-mbean.png! > Screencast: > http://screencast.com/t/Tyc0isAane > I understand that the tooling must keep refreshing the mbeans list (probably), but it's annoying to keep blinking in the status bar like this. We should probably remove that message. > A minor issue is that the wording seems odd. Shouldn't it be "Refreshing MBean section..." or something like that? I'm not sure what the convention is here. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14525) "Create Arquillian Deployment Method" should scan for depending classes on add

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14525?page=com.atlassian.jira.plugi... ] Aslak Knutsen commented on JBIDE-14525: --------------------------------------- This looks really nice.. A little suggestion, I'll open a new case if needed, but.. How about grouping each dependent class for the same package in a addClasses(X, Y) instead of using addClass on all individually. Just makes the Deployment a bit more visually 'appealing'. In theory addClasses could be more optimized when adding multiple in one call. {code} org.test.a.X org.test.a.Y org.test.b.Z .addClasses(X, Y) .addClass(Z) {code} ? > "Create Arquillian Deployment Method" should scan for depending classes on add > ------------------------------------------------------------------------------ > > Key: JBIDE-14525 > URL: https://issues.jboss.org/browse/JBIDE-14525 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: testing-tools > Reporter: Aslak Knutsen > Assignee: Snjezana Peco > Labels: new_and_noteworthy > Fix For: 4.2.0.Alpha1 > > > When you add 'classes' to the deployment, the wizard should scan the class for depending types and suggest them to be added as well. > Example: https://github.com/aslakknutsen/arquillian-plugin-test > Given the Deployment Wizard > When 'add class' TestHandler > Then suggest to also add SuperTestHandler(SuperClass) and Handler(Field) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18259) Refresh MBean section keeps blinking in the status bar

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18259?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18259: --------------------------------------------- I agree if it is a constant background job its better to put in as a system background job. btw. I guess this runs very fast locally which explains why I haven't noticed it much. > Refresh MBean section keeps blinking in the status bar > ------------------------------------------------------ > > Key: JBIDE-18259 > URL: https://issues.jboss.org/browse/JBIDE-18259 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR2 > > Attachments: refresh-mbean.png > > > When you connect to a local process in the JMX Navigator and then check out some mbeans in the Properties view, there will be a "Refresh MBean section" message blinking in the status bar at the bottom of Eclipse every second or so. > Screenshot: > !refresh-mbean.png! > Screencast: > http://screencast.com/t/Tyc0isAane > I understand that the tooling must keep refreshing the mbeans list (probably), but it's annoying to keep blinking in the status bar like this. We should probably remove that message. > A minor issue is that the wording seems odd. Shouldn't it be "Refreshing MBean section..." or something like that? I'm not sure what the convention is here. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18264) Weird JMX entries in server view

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18264?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-18264: ------------------------------------- Regression from https://issues.jboss.org/browse/JBIDE-18183, which was meant to more efficiently add connections to the JMX view only. > Weird JMX entries in server view > -------------------------------- > > Key: JBIDE-18264 > URL: https://issues.jboss.org/browse/JBIDE-18264 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.2.0.CR1 > > Attachments: weird-entries-2.png, weird-entries.png > > > When I start EAP 6, two new entries appear in the Server view: > [Disconnected] > [Disconnected] > !weird-entries.png! > That looks pretty weird. > I can right-click them and connect and they actually correspond to the two server entries in JMX Navigator - one in Local Processes, the other in Server Connections. But there is nothing else I can do with these in the server views. What's the point of having it there? I find it confusing, especially since there is no explanations whatsoever about what these are. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18136) iBeacon plugin problem, can´t compile app

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18136?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-18136: --------------------------------- Fix Version/s: 4.2.x > iBeacon plugin problem, can´t compile app > ----------------------------------------- > > Key: JBIDE-18136 > URL: https://issues.jboss.org/browse/JBIDE-18136 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Reporter: eduardo de souza > Assignee: Gorkem Ercan > Priority: Critical > Fix For: 4.2.x > > > I have created a Hybrid Mobile App, then added an iBeacon plugin: > https://github.com/petermetz/cordova-plugin-ibeacon.git > Then I tried to compile to see if there was any problem. I got this message: > An internal error occurred during: "Launching TesteApp4 (Android Device)". > java.lang.NullPointerException -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18264) Weird JMX entries in server view

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18264?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-18264: ------------------------------------- Good catch, just saw them last night and then noticed you had already opened a jira for it. Will work on it. > Weird JMX entries in server view > -------------------------------- > > Key: JBIDE-18264 > URL: https://issues.jboss.org/browse/JBIDE-18264 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.2.0.CR1 > > Attachments: weird-entries-2.png, weird-entries.png > > > When I start EAP 6, two new entries appear in the Server view: > [Disconnected] > [Disconnected] > !weird-entries.png! > That looks pretty weird. > I can right-click them and connect and they actually correspond to the two server entries in JMX Navigator - one in Local Processes, the other in Server Connections. But there is nothing else I can do with these in the server views. What's the point of having it there? I find it confusing, especially since there is no explanations whatsoever about what these are. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18259) Refresh MBean section keeps blinking in the status bar

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18259?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-18259: ------------------------------------- We had at one time discussed making it a background / system job, but it was decided that that was poor form, to be constantly doing things without the user knowing. I'll defer to [~maxandersen] to make a decision on this a second time. To be honest, I'm not sure its appropriate for ti to be refreshing the jmx tree so often anyway, but the user does have a setting to customize the duration in the preference pages, which they should make use of. I would imagine the tree should just refresh if the user requests a refresh, but, jvmmonitor was not coded that way and I haven't had time to dig into the deep parts of its code. > Refresh MBean section keeps blinking in the status bar > ------------------------------------------------------ > > Key: JBIDE-18259 > URL: https://issues.jboss.org/browse/JBIDE-18259 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR2 > > Attachments: refresh-mbean.png > > > When you connect to a local process in the JMX Navigator and then check out some mbeans in the Properties view, there will be a "Refresh MBean section" message blinking in the status bar at the bottom of Eclipse every second or so. > Screenshot: > !refresh-mbean.png! > Screencast: > http://screencast.com/t/Tyc0isAane > I understand that the tooling must keep refreshing the mbeans list (probably), but it's annoying to keep blinking in the status bar like this. We should probably remove that message. > A minor issue is that the wording seems odd. Shouldn't it be "Refreshing MBean section..." or something like that? I'm not sure what the convention is here. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18121) CordovaSim losing Ionic's Header

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18121?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov updated JBIDE-18121: ------------------------------------------- Assignee: Ilya Buziuk > CordovaSim losing Ionic's Header > -------------------------------- > > Key: JBIDE-18121 > URL: https://issues.jboss.org/browse/JBIDE-18121 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.2.0.CR1 > Reporter: Burr Sutter > Assignee: Ilya Buziuk > Fix For: 4.2.0.Final > > Attachments: Screenshot1.png > > > See Video: > http://screencast.com/t/MOIwR6dOJpNs > I am using "ionic start demoapp sidemenu" - when the menu is activated and an option selected then the header will disappear. I included a demo of the iOS Simulator as well. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17626) provide extension points for customizing node name and icon in JMX explorer

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17626?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-17626. --------------------------------- Resolution: Partially Completed The designed API had only a label provider, no tooltip providers. The patch was committed along with https://issues.jboss.org/browse/JBIDE-18183 > provide extension points for customizing node name and icon in JMX explorer > --------------------------------------------------------------------------- > > Key: JBIDE-17626 > URL: https://issues.jboss.org/browse/JBIDE-17626 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jmx > Affects Versions: 4.2.0.Beta3 > Reporter: Lars Heinemann > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.2.0.CR1 > > > Currently the whole naming and icon assignment is done in jmx.local plugin inside JBT. If other projects want to provide own icons or names for nodes it is currently not possible. We should also provide some priority mechanism if more than one plugin wants to customize a node in the tree. > Tasks: > # provide an extension point for customizing the label of the process node > # provide an extension point for customizing the icon of the process node > # provide an extension point for customizing the tooltip of the process node > # have some priority logic to decide what plugin is actually customizing it if there is more than one provider > # hand over the output of jps to determine the name, icon and tooltip -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17626) provide extension points for customizing node name and icon in JMX explorer

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17626?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-17626: -------------------------------- Labels: respin-a (was: ) > provide extension points for customizing node name and icon in JMX explorer > --------------------------------------------------------------------------- > > Key: JBIDE-17626 > URL: https://issues.jboss.org/browse/JBIDE-17626 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jmx > Affects Versions: 4.2.0.Beta3 > Reporter: Lars Heinemann > Labels: respin-a > Fix For: 4.2.0.CR1 > > > Currently the whole naming and icon assignment is done in jmx.local plugin inside JBT. If other projects want to provide own icons or names for nodes it is currently not possible. We should also provide some priority mechanism if more than one plugin wants to customize a node in the tree. > Tasks: > # provide an extension point for customizing the label of the process node > # provide an extension point for customizing the icon of the process node > # provide an extension point for customizing the tooltip of the process node > # have some priority logic to decide what plugin is actually customizing it if there is more than one provider > # hand over the output of jps to determine the name, icon and tooltip -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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 September 2014