June 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17513) Searching in plugin registry is slow and UI blocking.

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-17513: ---------------------------------- Summary: Searching in plugin registry is slow and UI blocking. Key: JBIDE-17513 URL: https://issues.jboss.org/browse/JBIDE-17513 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid Affects Versions: 4.2.0.Beta2 Environment: Fedora 20, openJDK 1.7.0_55 Reporter: Radim Hopp Serching in plugin registry on CordovaPluginSelectionPage of NewHybridProjectWizard takes about 5-6 seconds during which the UI is not responsive. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3057) JBDS causes "not responding" message on RHEL

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3057?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3057: -------------------------------- Component/s: upstream (was: ui/branding) > JBDS causes "not responding" message on RHEL > -------------------------------------------- > > Key: JBDS-3057 > URL: https://issues.jboss.org/browse/JBDS-3057 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: upstream > Affects Versions: 7.1.1.GA > Environment: RHEL 7 Beta > OpenJDK 1.7 > JBDS 7.1.1 > Reporter: Martin Malina > Assignee: Denis Golovin > Fix For: 8.0.0.Beta3 > > Attachments: jbds-not-responding.png > > > I was smoke testing JBDS 7 on RHEL 7 Beta and every time I started JBDS with a new workspace, I got a "not responding" window where I could either force quit JBDS or wait. > Obviously this is due to some limit that is set in the OS and when reached, this popup is shown. > On subsequent starts of JBDS with the same workspace, this does not happen. > The system was a VirtualBox VM run on Windows, but there was nothing else happening on the machine, so this shouldn't slow things down too much. Also, the machine has 8 GB of RAM out of which 4 GB was dedicated to the VM. So I don't think the HW is particularly slow. > I understand that this JIRA is very vague, but maybe it's worth trying to find if it's caused by some synchronous processes that we run at JBDS start. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3057) JBDS causes "not responding" message on RHEL

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3057?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3057: -------------------------------- Component/s: ui/branding > JBDS causes "not responding" message on RHEL > -------------------------------------------- > > Key: JBDS-3057 > URL: https://issues.jboss.org/browse/JBDS-3057 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ui/branding > Affects Versions: 7.1.1.GA > Environment: RHEL 7 Beta > OpenJDK 1.7 > JBDS 7.1.1 > Reporter: Martin Malina > Assignee: Denis Golovin > Fix For: 8.0.0.Beta3 > > Attachments: jbds-not-responding.png > > > I was smoke testing JBDS 7 on RHEL 7 Beta and every time I started JBDS with a new workspace, I got a "not responding" window where I could either force quit JBDS or wait. > Obviously this is due to some limit that is set in the OS and when reached, this popup is shown. > On subsequent starts of JBDS with the same workspace, this does not happen. > The system was a VirtualBox VM run on Windows, but there was nothing else happening on the machine, so this shouldn't slow things down too much. Also, the machine has 8 GB of RAM out of which 4 GB was dedicated to the VM. So I don't think the HW is particularly slow. > I understand that this JIRA is very vague, but maybe it's worth trying to find if it's caused by some synchronous processes that we run at JBDS start. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3057) JBDS causes "not responding" message on RHEL

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3057?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3057: ------------------------------ Fix Version/s: 8.0.0.Beta3 > JBDS causes "not responding" message on RHEL > -------------------------------------------- > > Key: JBDS-3057 > URL: https://issues.jboss.org/browse/JBDS-3057 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 7.1.1.GA > Environment: RHEL 7 Beta > OpenJDK 1.7 > JBDS 7.1.1 > Reporter: Martin Malina > Assignee: Denis Golovin > Fix For: 8.0.0.Beta3 > > Attachments: jbds-not-responding.png > > > I was smoke testing JBDS 7 on RHEL 7 Beta and every time I started JBDS with a new workspace, I got a "not responding" window where I could either force quit JBDS or wait. > Obviously this is due to some limit that is set in the OS and when reached, this popup is shown. > On subsequent starts of JBDS with the same workspace, this does not happen. > The system was a VirtualBox VM run on Windows, but there was nothing else happening on the machine, so this shouldn't slow things down too much. Also, the machine has 8 GB of RAM out of which 4 GB was dedicated to the VM. So I don't think the HW is particularly slow. > I understand that this JIRA is very vague, but maybe it's worth trying to find if it's caused by some synchronous processes that we run at JBDS start. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3057) JBDS causes "not responding" message on RHEL

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3057?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3057: ------------------------------ Assignee: Denis Golovin (was: Fred Bricon) > JBDS causes "not responding" message on RHEL > -------------------------------------------- > > Key: JBDS-3057 > URL: https://issues.jboss.org/browse/JBDS-3057 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 7.1.1.GA > Environment: RHEL 7 Beta > OpenJDK 1.7 > JBDS 7.1.1 > Reporter: Martin Malina > Assignee: Denis Golovin > Attachments: jbds-not-responding.png > > > I was smoke testing JBDS 7 on RHEL 7 Beta and every time I started JBDS with a new workspace, I got a "not responding" window where I could either force quit JBDS or wait. > Obviously this is due to some limit that is set in the OS and when reached, this popup is shown. > On subsequent starts of JBDS with the same workspace, this does not happen. > The system was a VirtualBox VM run on Windows, but there was nothing else happening on the machine, so this shouldn't slow things down too much. Also, the machine has 8 GB of RAM out of which 4 GB was dedicated to the VM. So I don't think the HW is particularly slow. > I understand that this JIRA is very vague, but maybe it's worth trying to find if it's caused by some synchronous processes that we run at JBDS start. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3057) JBDS causes "not responding" message on RHEL

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3057?page=com.atlassian.jira.plugin.... ] Fred Bricon reassigned JBDS-3057: --------------------------------- Assignee: Fred Bricon > JBDS causes "not responding" message on RHEL > -------------------------------------------- > > Key: JBDS-3057 > URL: https://issues.jboss.org/browse/JBDS-3057 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 7.1.1.GA > Environment: RHEL 7 Beta > OpenJDK 1.7 > JBDS 7.1.1 > Reporter: Martin Malina > Assignee: Fred Bricon > Attachments: jbds-not-responding.png > > > I was smoke testing JBDS 7 on RHEL 7 Beta and every time I started JBDS with a new workspace, I got a "not responding" window where I could either force quit JBDS or wait. > Obviously this is due to some limit that is set in the OS and when reached, this popup is shown. > On subsequent starts of JBDS with the same workspace, this does not happen. > The system was a VirtualBox VM run on Windows, but there was nothing else happening on the machine, so this shouldn't slow things down too much. Also, the machine has 8 GB of RAM out of which 4 GB was dedicated to the VM. So I don't think the HW is particularly slow. > I understand that this JIRA is very vague, but maybe it's worth trying to find if it's caused by some synchronous processes that we run at JBDS start. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17488) Forge2: project-specific wizards are not visible on Ctrl+4

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17488?page=com.atlassian.jira.plugi... ] Michelle Murray commented on JBIDE-17488: ----------------------------------------- I noticed that if in the Project Explorer view I select an item and immediately press Ctrl+4, then it does show me project-specific Forge wizards. But if I am in the same place in the Forge CLI and press Ctrl+4, then it doesn't show me the project-specific wizards. > Forge2: project-specific wizards are not visible on Ctrl+4 > ---------------------------------------------------------- > > Key: JBIDE-17488 > URL: https://issues.jboss.org/browse/JBIDE-17488 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Beta2 > Environment: Fedora19, GTK2 + GTK3, OpenJDK7 > Reporter: Michelle Murray > Priority: Blocker > > JBDS-2734 states the following: > {quote} > * The availability of the wizards is depending on the initial selection when hitting the above key combo. > => with nothing selected there are wizards for managing connection profiles and Forge addons and for creating new projects. > => with e.g. a project selected there will be wizards for setting up support for JPA, JSF, and so on as well as for creating classes, generating entities, scaffolding a user interface, etc. > {quote} > After starting forge2, I navigate to my project > {noformat} > [workspace]$ cd my-mobile-app > [my-mobile-app]$ > {noformat} > Tab (eventually) provides a list of forge2 possible commands, of which jpa-new-entity is one. > Ctrl+4 opens the forge2 wizards list window but only the wizards for connections, addons and new project are displayed. > Navigating down to scr/com/company/example/mymobileapp/model again only shows the wizards for connections, addons and new project. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17488) Forge2: project-specific wizards are not visible on Ctrl+4 from CLI

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17488?page=com.atlassian.jira.plugi... ] Michelle Murray updated JBIDE-17488: ------------------------------------ Summary: Forge2: project-specific wizards are not visible on Ctrl+4 from CLI (was: Forge2: project-specific wizards are not visible on Ctrl+4) > Forge2: project-specific wizards are not visible on Ctrl+4 from CLI > ------------------------------------------------------------------- > > Key: JBIDE-17488 > URL: https://issues.jboss.org/browse/JBIDE-17488 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Beta2 > Environment: Fedora19, GTK2 + GTK3, OpenJDK7 > Reporter: Michelle Murray > Priority: Blocker > > JBDS-2734 states the following: > {quote} > * The availability of the wizards is depending on the initial selection when hitting the above key combo. > => with nothing selected there are wizards for managing connection profiles and Forge addons and for creating new projects. > => with e.g. a project selected there will be wizards for setting up support for JPA, JSF, and so on as well as for creating classes, generating entities, scaffolding a user interface, etc. > {quote} > After starting forge2, I navigate to my project > {noformat} > [workspace]$ cd my-mobile-app > [my-mobile-app]$ > {noformat} > Tab (eventually) provides a list of forge2 possible commands, of which jpa-new-entity is one. > Ctrl+4 opens the forge2 wizards list window but only the wizards for connections, addons and new project are displayed. > Navigating down to scr/com/company/example/mymobileapp/model again only shows the wizards for connections, addons and new project. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17506) Missing VJET plugin in Central

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17506?page=com.atlassian.jira.plugi... ] Marián Labuda resolved JBIDE-17506. ----------------------------------- Labels: respin-a (was: ) Fix Version/s: 4.2.0.Beta2 Resolution: Done I didn't notice that VJET is now in early access. Problem solved. > Missing VJET plugin in Central > ------------------------------ > > Key: JBIDE-17506 > URL: https://issues.jboss.org/browse/JBIDE-17506 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.2.0.Beta2 > Reporter: Marián Labuda > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.Beta2 > > > JBT 4.2.0.Beta2a (respin-a) central does not containt VJET plugin. Also in JBDS 8.0.0.Beta2a build B106 is not VJET plugin listed. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17506) Missing VJET plugin in Central

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17506?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-17506. --------------------------------- Assignee: Marián Labuda Resolution: Rejected > Missing VJET plugin in Central > ------------------------------ > > Key: JBIDE-17506 > URL: https://issues.jboss.org/browse/JBIDE-17506 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.2.0.Beta2 > Reporter: Marián Labuda > Assignee: Marián Labuda > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.Beta2 > > > JBT 4.2.0.Beta2a (respin-a) central does not containt VJET plugin. Also in JBDS 8.0.0.Beta2a build B106 is not VJET plugin listed. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

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