October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15617) Forge New Project UI Wizard hangs

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15617?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15617: ---------------------------------------- Fix Version/s: 4.1.1.Alpha2 (was: 4.1.0.1.Final) > Forge New Project UI Wizard hangs > --------------------------------- > > Key: JBIDE-15617 > URL: https://issues.jboss.org/browse/JBIDE-15617 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Final > Reporter: Pavol Srna > Fix For: 4.1.1.Alpha2 > > Attachments: eclipse_jstack.txt, forge-new-project.png, forge_jstack.txt, wizard.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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15617) Forge New Project UI Wizard hangs

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15617?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-15617: ------------------------------------ No, we missed that issue in 4.1.0 too. > Forge New Project UI Wizard hangs > --------------------------------- > > Key: JBIDE-15617 > URL: https://issues.jboss.org/browse/JBIDE-15617 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Final > Reporter: Pavol Srna > Fix For: 4.1.0.1.Final > > Attachments: eclipse_jstack.txt, forge-new-project.png, forge_jstack.txt, wizard.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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15623) An icon for "Report error" dialog and menu

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15623?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-15623: -------------------------------------- Assignee: Daniel Azarov > An icon for "Report error" dialog and menu > ------------------------------------------ > > Key: JBIDE-15623 > URL: https://issues.jboss.org/browse/JBIDE-15623 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Affects Versions: 4.1.1.Alpha1 > Reporter: Mickael Istria > Assignee: Daniel Azarov > > The "Report Error" menu should have an icon, such as a bug, and something that looks like a small explosion (see http://www.colourbox.com/preview/2953774-167726-pop-art-comic-style-explo... ). This icon should be put in menu, and could also be used in dialog. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15623) An icon for "Report error" dialog and menu

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15623?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-15623: ----------------------------------- Fix Version/s: 4.2.0.Alpha1 > An icon for "Report error" dialog and menu > ------------------------------------------ > > Key: JBIDE-15623 > URL: https://issues.jboss.org/browse/JBIDE-15623 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Affects Versions: 4.1.1.Alpha1 > Reporter: Mickael Istria > Assignee: Daniel Azarov > Fix For: 4.2.0.Alpha1 > > > The "Report Error" menu should have an icon, such as a bug, and something that looks like a small explosion (see http://www.colourbox.com/preview/2953774-167726-pop-art-comic-style-explo... ). This icon should be put in menu, and could also be used in dialog. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15620) Wrong CDI warnings

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15620?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-15620: -------------------------------------- Assignee: Viacheslav Kabanovich Slava, could you please check if these injections work in JBT 4.2 > Wrong CDI warnings > ------------------ > > Key: JBIDE-15620 > URL: https://issues.jboss.org/browse/JBIDE-15620 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.1.1.Alpha1 > Reporter: Juergen Zimmermann > Assignee: Viacheslav Kabanovich > Fix For: 4.2.x > > Attachments: wrong-cdi-warnings.png > > > I moved to WildFly (and therefore to Weld 2.0.CR1 resp CDI 1.1). I'm getting warnings about wrong dependency injection of these classes: > * HttpSession > * HttpServletRequest > But the CDI 1.1 spec allows them to be injected (and my web app works fine). > I'll attach a stacktrace to illustrate the wrong warnings -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15620) Wrong CDI warnings

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15620?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-15620: ----------------------------------- Fix Version/s: 4.2.x > Wrong CDI warnings > ------------------ > > Key: JBIDE-15620 > URL: https://issues.jboss.org/browse/JBIDE-15620 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.1.1.Alpha1 > Reporter: Juergen Zimmermann > Fix For: 4.2.x > > Attachments: wrong-cdi-warnings.png > > > I moved to WildFly (and therefore to Weld 2.0.CR1 resp CDI 1.1). I'm getting warnings about wrong dependency injection of these classes: > * HttpSession > * HttpServletRequest > But the CDI 1.1 spec allows them to be injected (and my web app works fine). > I'll attach a stacktrace to illustrate the wrong warnings -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15617) Forge New Project UI Wizard hangs

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15617?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15617: --------------------------------------------- is this a new issue in 4.1.0.1 or same behavior seen in 4.1.0 ? > Forge New Project UI Wizard hangs > --------------------------------- > > Key: JBIDE-15617 > URL: https://issues.jboss.org/browse/JBIDE-15617 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Final > Reporter: Pavol Srna > Fix For: 4.1.0.1.Final > > Attachments: eclipse_jstack.txt, forge-new-project.png, forge_jstack.txt, wizard.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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15620) Wrong CDI warnings

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15620?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-15620: ---------------------------------------- JBoss Tools 4.1.x does not support CDI 1.1. We are working on it in JBT 4.2 - JBIDE-13228 > Wrong CDI warnings > ------------------ > > Key: JBIDE-15620 > URL: https://issues.jboss.org/browse/JBIDE-15620 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.1.1.Alpha1 > Reporter: Juergen Zimmermann > Attachments: wrong-cdi-warnings.png > > > I moved to WildFly (and therefore to Weld 2.0.CR1 resp CDI 1.1). I'm getting warnings about wrong dependency injection of these classes: > * HttpSession > * HttpServletRequest > But the CDI 1.1 spec allows them to be injected (and my web app works fine). > I'll attach a stacktrace to illustrate the wrong warnings -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15614) Rename EAP 6.1 server type to 6.1+, ensure runtime detection is accurate

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15614?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15614: --------------------------------------------- actually - might be Rob's additional fix removed that warning. Point is still that the warning is expected to be there until we know for sure EAP 6.2 works ;) > Rename EAP 6.1 server type to 6.1+, ensure runtime detection is accurate > ------------------------------------------------------------------------ > > Key: JBIDE-15614 > URL: https://issues.jboss.org/browse/JBIDE-15614 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection, server > Affects Versions: 4.1.0.Final > Environment: JBDS 7.0.0.GA > Reporter: Martin Malina > Assignee: Max Rydahl Andersen > Fix For: 4.1.1.Beta1 > > > 1. When you try to add EAP 6.2 using runtime detection, it detects it as EAP 6.0. > 2. When trying to add EAP 6.2 manually, there is no type EAP 6.2 > Let me know if you want subtasks for these two. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15614) Rename EAP 6.1 server type to 6.1+, ensure runtime detection is accurate

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15614?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15614: --------------------------------------------- [~mmalina] no, this fix simply allow 6.2 to be runtime detected. JBIDE-15619 is what [~rob.stryker] opened to capture "full support" for EAP 6.2. Note, this warning is what what we show to indicate we don't recognize a new server fully - if you got recommendations for rewording it to be less "scary" is welcome ;) > Rename EAP 6.1 server type to 6.1+, ensure runtime detection is accurate > ------------------------------------------------------------------------ > > Key: JBIDE-15614 > URL: https://issues.jboss.org/browse/JBIDE-15614 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection, server > Affects Versions: 4.1.0.Final > Environment: JBDS 7.0.0.GA > Reporter: Martin Malina > Assignee: Max Rydahl Andersen > Fix For: 4.1.1.Beta1 > > > 1. When you try to add EAP 6.2 using runtime detection, it detects it as EAP 6.0. > 2. When trying to add EAP 6.2 manually, there is no type EAP 6.2 > Let me know if you want subtasks for these two. -- 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, 6 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 October 2013