February 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-16495) The Forge 2 console starts before the runtime is started

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16495?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-16495: ------------------------------- Attachment: forge-hang.png eclipse.jstack > The Forge 2 console starts before the runtime is started > -------------------------------------------------------- > > Key: JBIDE-16495 > URL: https://issues.jboss.org/browse/JBIDE-16495 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.Alpha2 > > Attachments: eclipse.jstack, forge-hang.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16495) The Forge 2 console starts before the runtime is started

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16495?page=com.atlassian.jira.plugi... ] Pavol Srna edited comment on JBIDE-16495 at 2/17/14 10:19 AM: -------------------------------------------------------------- Unfortunately doesn't work for me. If I attempt to open Window -> Show View -> Forge -> F2 Console then there is a dialog window saying "Please wait while Forge 2 is started" but it never finish. was (Author: psrna): Verified in JBT 4.2.0.Alpha2b. > The Forge 2 console starts before the runtime is started > -------------------------------------------------------- > > Key: JBIDE-16495 > URL: https://issues.jboss.org/browse/JBIDE-16495 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.Alpha2 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16023) Publishing of exploded projects to remote servers is very slow - Luna

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16023?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-16023. --------------------------------- Verified in JBDS 8.0.0.Alpha2b B71. It still takes considerably longer (over slow connection) than zip deployments, but it's nowhere near as bad as it used to be. > Publishing of exploded projects to remote servers is very slow - Luna > --------------------------------------------------------------------- > > Key: JBIDE-16023 > URL: https://issues.jboss.org/browse/JBIDE-16023 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Martin Malina > Assignee: Martin Malina > Priority: Critical > Fix For: 4.2.0.Alpha1 > > > When you try to publish something to a remote server and the deployment is set to exploded archives (i.e. the default), it is very slow. For example the java ee web project from Central takes several minutes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16480) AS Tool don't detect running instance when starting a server anymore

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16480?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-16480: ---------------------------------- Fix Version/s: 4.2.0.Beta1 (was: 4.2.0.Alpha2) > AS Tool don't detect running instance when starting a server anymore > -------------------------------------------------------------------- > > Key: JBIDE-16480 > URL: https://issues.jboss.org/browse/JBIDE-16480 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Rob Stryker > Fix For: 4.2.0.Beta1 > > > if I had an AS 7.1 server already running (in a previous workbench instance for example), JBT would pop a dialog asking me to use/connect to the existing instance. Now, I don't see it anymore and I get errors during server start-up (bind failure - address already in use) and server is in "started" mode (I guess the tooling managed to connect to the mgmt port) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16343) "Materialize Libraries" is not obvious

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16343?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-16343. ------------------------------------ verified in JBDS 8.0.0 Alpha2-v20140212-2251-B70 > "Materialize Libraries" is not obvious > -------------------------------------- > > Key: JBIDE-16343 > URL: https://issues.jboss.org/browse/JBIDE-16343 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: maven > Affects Versions: 4.2.0.Alpha1 > Reporter: Mickael Istria > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.2.0.Alpha2 > > > While looking at [~fbricon] doing a demo I (and [~FroMage] and [~xcoulon]) felt that "Materialize Libraries" is not a clear name for what it does. > Why not renaming it to "Copy libraries into Project..." or "Turn into Libraries inside project..." ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15944) [Regression] Can not edit server runtime classpath

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15944?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-15944. --------------------------------- Verified once more to be sure - cannot replicate in JBDS 8.0.0.Alpha2b B71. Closing. > [Regression] Can not edit server runtime classpath > -------------------------------------------------- > > Key: JBIDE-15944 > URL: https://issues.jboss.org/browse/JBIDE-15944 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.0.1.Final > Environment: windows eclipse 3.4.1 > Reporter: filippo rossoni > Assignee: Rob Stryker > Labels: new_and_noteworthy, regression > Fix For: 4.2.0.Alpha1 > > Attachments: JBIDE-3770.jpg > > > when edit the server runtime configuration the changes are lost after save -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16592) Allow to update/remove software installed from Central

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16592?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-16592: ----------------------------------- Attachment: JBIDE-16592-wip.jpeg Here is a screenshoft of suggested implementation. The general change is to allow multiple actions on a given discovery entry Ideas of improvements are to wrap text on first column, and have different colors. [~maxandersen] [~mmurray]: What do you think about this approach (using combo and text instead of checkbox) ? !JBIDE-16592-wip.jpeg! > Allow to update/remove software installed from Central > ------------------------------------------------------ > > Key: JBIDE-16592 > URL: https://issues.jboss.org/browse/JBIDE-16592 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Fix For: 4.2.0.Beta1 > > Attachments: JBIDE-16592-wip.jpeg > > > Central software page should allow user to update or uninstall some modules. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16599) New server dialog error - home directory does not exist

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16599?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-16599: ---------------------------------- Description: This is not a regression, it's always been like that, but I consider it a bug. When you're adding a server, in the dialog you're asked for the jboss home dir. But this field is pre-filled with something like this: /usr/bin/jboss-eap-6.1+.x This causes an error shown at the top: The home directory does not exist or is not a directory. !add-server-bogus-path.png! I understand that the goal here was to make life easier for those who have EAP/AS/WF installed in a standard location - perhaps with rpm installation, although I doubt this would be the actual path anyway. This violates the Eclipse UI guidelines found here in section 5.3: http://www.eclipse.org/articles/Article-UI-Guidelines/Contents.html#Wizards I would suggest leaving the field empty by default (and ensuring that the guideline is fulfilled). Another option would be to check if we can find an installation in the default path, then use it, otherwise leave empty. was: This is not a regression, it's always been like that, but I consider it a bug. When you're adding a server, in the dialog you're asked for the jboss home dir. But this field is pre-filled with something like this: /usr/bin/jboss-eap-6.1+.x This causes an error shown at the top: The home directory does not exist or is not a directory. I understand that the goal here was to make life easier for those who have EAP/AS/WF installed in a standard location - perhaps with rpm installation, although I doubt this would be the actual path anyway. This violates the Eclipse UI guidelines found here in section 5.3: http://www.eclipse.org/articles/Article-UI-Guidelines/Contents.html#Wizards I would suggest leaving the field empty by default (and ensuring that the guideline is fulfilled). Another option would be to check if we can find an installation in the default path, then use it, otherwise leave empty. > New server dialog error - home directory does not exist > ------------------------------------------------------- > > Key: JBIDE-16599 > URL: https://issues.jboss.org/browse/JBIDE-16599 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Alpha2 > Environment: JBDS 8.0.0.Alpha2b B71 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.Beta1 > > Attachments: add-server-bogus-path.png > > > This is not a regression, it's always been like that, but I consider it a bug. > When you're adding a server, in the dialog you're asked for the jboss home dir. But this field is pre-filled with something like this: > /usr/bin/jboss-eap-6.1+.x > This causes an error shown at the top: > The home directory does not exist or is not a directory. > !add-server-bogus-path.png! > I understand that the goal here was to make life easier for those who have EAP/AS/WF installed in a standard location - perhaps with rpm installation, although I doubt this would be the actual path anyway. > This violates the Eclipse UI guidelines found here in section 5.3: > http://www.eclipse.org/articles/Article-UI-Guidelines/Contents.html#Wizards > I would suggest leaving the field empty by default (and ensuring that the guideline is fulfilled). Another option would be to check if we can find an installation in the default path, then use it, otherwise leave empty. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16599) New server dialog error - home directory does not exist

by Martin Malina (JIRA)

Martin Malina created JBIDE-16599: ------------------------------------- Summary: New server dialog error - home directory does not exist Key: JBIDE-16599 URL: https://issues.jboss.org/browse/JBIDE-16599 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.2.0.Alpha2 Environment: JBDS 8.0.0.Alpha2b B71 Reporter: Martin Malina Assignee: Rob Stryker Fix For: 4.2.0.Beta1 Attachments: add-server-bogus-path.png This is not a regression, it's always been like that, but I consider it a bug. When you're adding a server, in the dialog you're asked for the jboss home dir. But this field is pre-filled with something like this: /usr/bin/jboss-eap-6.1+.x This causes an error shown at the top: The home directory does not exist or is not a directory. I understand that the goal here was to make life easier for those who have EAP/AS/WF installed in a standard location - perhaps with rpm installation, although I doubt this would be the actual path anyway. This violates the Eclipse UI guidelines found here in section 5.3: http://www.eclipse.org/articles/Article-UI-Guidelines/Contents.html#Wizards I would suggest leaving the field empty by default (and ensuring that the guideline is fulfilled). Another option would be to check if we can find an installation in the default path, then use it, otherwise leave empty. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16599) New server dialog error - home directory does not exist

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16599?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-16599: ---------------------------------- Attachment: add-server-bogus-path.png > New server dialog error - home directory does not exist > ------------------------------------------------------- > > Key: JBIDE-16599 > URL: https://issues.jboss.org/browse/JBIDE-16599 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Alpha2 > Environment: JBDS 8.0.0.Alpha2b B71 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.Beta1 > > Attachments: add-server-bogus-path.png > > > This is not a regression, it's always been like that, but I consider it a bug. > When you're adding a server, in the dialog you're asked for the jboss home dir. But this field is pre-filled with something like this: > /usr/bin/jboss-eap-6.1+.x > This causes an error shown at the top: > The home directory does not exist or is not a directory. > I understand that the goal here was to make life easier for those who have EAP/AS/WF installed in a standard location - perhaps with rpm installation, although I doubt this would be the actual path anyway. > This violates the Eclipse UI guidelines found here in section 5.3: > http://www.eclipse.org/articles/Article-UI-Guidelines/Contents.html#Wizards > I would suggest leaving the field empty by default (and ensuring that the guideline is fulfilled). Another option would be to check if we can find an installation in the default path, then use it, otherwise leave empty. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 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 February 2014