February 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-16050) CLONE - OpenShift: Wrong title of Manage SSH keys shell

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16050?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-16050. --------------------------------- Verified in JBT 4.2.0.Alpha1. > CLONE - OpenShift: Wrong title of Manage SSH keys shell > ------------------------------------------------------- > > Key: JBIDE-16050 > URL: https://issues.jboss.org/browse/JBIDE-16050 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.0.Alpha1 > > Attachments: manage-ssh-keys.png, wrong_title.png > > > Manage SSH key shell (invoked from context menu of connection in the OpenShift Explorer) has title Select Domain instead of something like "Manage SSH keys"... > See attached image -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16419) JUnit Test failure: investigate time out/deadlock in JSF UI JUnit Tests

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16419?page=com.atlassian.jira.plugi... ] Victor Rubezhny edited comment on JBIDE-16419 at 2/4/14 4:13 AM: ----------------------------------------------------------------- Doesn't look like a deadlock, but does look like a hang (infinite loop) in native code: [Bug 354842 - Hang in org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)|https://bugs.eclipse.org/bugs/show_bug.cgi?id=354842] was (Author: vrubezhny): Doesn't look like a deadlock, but do look like a hang in native code: [Bug 354842 - Hang in org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)|https://bugs.eclipse.org/bugs/show_bug.cgi?id=354842] > JUnit Test failure: investigate time out/deadlock in JSF UI JUnit Tests > ----------------------------------------------------------------------- > > Key: JBIDE-16419 > URL: https://issues.jboss.org/browse/JBIDE-16419 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.Alpha1 > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Fix For: 4.2.0.Alpha2 > > Attachments: jstack.27042.log > > > Sometimes JUnit Tests for jbosstools-javaee component fail with timeout (probably deadlocked). > See example stacktrace attached -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15775) Eclipse is not running newly created forge web project

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15775?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-15775. ------------------------------ Cannot reproduce either. > Eclipse is not running newly created forge web project > ------------------------------------------------------ > > Key: JBIDE-15775 > URL: https://issues.jboss.org/browse/JBIDE-15775 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Environment: Windows XP, Eclipse Kepler, Forge 1.3.2, Maven 3 > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.2.0.Alpha1 > > > I created a new forge project in Eclipse forge plugin > run scaffold to create a JSF project and when i right click the project i don't see Run as Server. I see a option of make as deplorable . its also not working. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15665) Application wizard: Wrong output directory in new Tomcat 7 applications

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15665?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-15665. --------------------------------- Verified in JBT 4.2.0.Alpha1. > Application wizard: Wrong output directory in new Tomcat 7 applications > ----------------------------------------------------------------------- > > Key: JBIDE-15665 > URL: https://issues.jboss.org/browse/JBIDE-15665 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.1.Final > Environment: Eclipse Kepler, Mac OS X 10.8.4 > Reporter: Jorge Yagüe París > Assignee: Andre Dietisheim > Labels: maven, tomcat7 > Fix For: 4.2.0.Alpha1 > > > I created a new Tomcat 7 Openshift application with the new project wizard, using an existing Maven project. The wizard adds the Openshift profile in pom.xml but outputDirectory is set as *deployments* instead of *webapps*, so when the application is pushed to the server it doesn't work. > Changing deployments to webapps in the Maven plugin makes it work. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16278) CLONE - Growl message does not appear or disappears prematurely

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16278?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-16278. ------------------------------ Verified in JBT 4.2.0.Alpha1. > CLONE - Growl message does not appear or disappears prematurely > --------------------------------------------------------------- > > Key: JBIDE-16278 > URL: https://issues.jboss.org/browse/JBIDE-16278 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.1.CR1 > Reporter: Pavol Srna > Assignee: Max Rydahl Andersen > Fix For: 4.2.0.Alpha1 > > -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16109) CLONE - Cmd+4/Forge menu should be possible to activate without having the forge shell active

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16109?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-16109. ------------------------------ Verified in JBT 4.2.0.Alpha1. Solved by inclusion of Forge2. > CLONE - Cmd+4/Forge menu should be possible to activate without having the forge shell active > --------------------------------------------------------------------------------------------- > > Key: JBIDE-16109 > URL: https://issues.jboss.org/browse/JBIDE-16109 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.2.0.Alpha1 > > > if the forge shell only is possible to show when the forge shell is in focus then its just a fancy ctrl+space thing. > Should be able to call it from outside of the forge UI so it becomes easily accessible. > Challenge is though to ensure forge is in the right directory - but taking the current selection as the directory to ensure forge is operating in should be enough. > Maybe the shell command should show the path for current selection so possible to know what context it will be executed in ? > Possibly even provide a "breadcrumb" style ui allowing users to click on a path segment to choose at what level it will operate. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16113) CLONE - Implement a 'Quick Access' Feature for Forge Commands

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16113?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-16113. ------------------------------ Verified in JBT 4.2.0.Alpha1 > CLONE - Implement a 'Quick Access' Feature for Forge Commands > ------------------------------------------------------------- > > Key: JBIDE-16113 > URL: https://issues.jboss.org/browse/JBIDE-16113 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.2.0.Alpha1 > > > Much like the Eclipse Quick Access Feature, pushing 'Cmd+4' should bring up a popup dialog with all the applicable commands. This involves creating a way for the Forge runtime and the Tools to communicate. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16111) CLONE - Cmd+4/Forge menu requires mouse to use, should be able to use keyboard like for Cmd+3

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16111?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-16111. ------------------------------ > CLONE - Cmd+4/Forge menu requires mouse to use, should be able to use keyboard like for Cmd+3 > --------------------------------------------------------------------------------------------- > > Key: JBIDE-16111 > URL: https://issues.jboss.org/browse/JBIDE-16111 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.2.0.Alpha1 > > -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15665) Application wizard: Wrong output directory in new Tomcat 7 applications

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15665?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-15665: ---------------------------------- Summary: Application wizard: Wrong output directory in new Tomcat 7 applications (was: Appliaction wizard: Wrong output directory in new Tomcat 7 applications) > Application wizard: Wrong output directory in new Tomcat 7 applications > ----------------------------------------------------------------------- > > Key: JBIDE-15665 > URL: https://issues.jboss.org/browse/JBIDE-15665 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.1.Final > Environment: Eclipse Kepler, Mac OS X 10.8.4 > Reporter: Jorge Yagüe París > Assignee: Andre Dietisheim > Labels: maven, tomcat7 > Fix For: 4.2.0.Alpha1 > > > I created a new Tomcat 7 Openshift application with the new project wizard, using an existing Maven project. The wizard adds the Openshift profile in pom.xml but outputDirectory is set as *deployments* instead of *webapps*, so when the application is pushed to the server it doesn't work. > Changing deployments to webapps in the Maven plugin makes it work. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15308) Application Details: Cannot copy application url

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15308?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-15308. --------------------------------- Verified in JBT 4.2.0.Alpha1. > Application Details: Cannot copy application url > ------------------------------------------------ > > Key: JBIDE-15308 > URL: https://issues.jboss.org/browse/JBIDE-15308 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.0.Alpha1 > > > # ASSERT: make sure that you have an application on OpenShift > # ASSERT: make sure that you have your connection defined in the OpenShift Explorer > # EXEC: in OpenShift Explorer: unfold your connection, select your application and choose *Details* in the context menu > # EXEC: in the upcoming dialog try to invoke the context menu on the value of the *Public URL* > Result: > There's no context menu in the cell with the value of the Public URL. The context menu appears in all other cells and offers *Copy* > Expected: > We should also have a context menu in the Public URL cell. -- 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, 5 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