March 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-10697) when pushing app the server says publishing and module says "synchronized"

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-10697: ------------------------------------------- Summary: when pushing app the server says publishing and module says "synchronized" Key: JBIDE-10697 URL: https://issues.jboss.org/browse/JBIDE-10697 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift, JBossAS/Servers Reporter: Max Rydahl Andersen Assignee: Andre Dietisheim Priority: Minor Fix For: 3.3.0.Beta1 module's says "synchronized" even though it is actually "Synchronzing" how to reproduce: publish large app with enough changes via openshift server to have it take enough time to show progress bar. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
6
0 / 0

[JBoss JIRA] (JBIDE-11359) support multiple ssh keys

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-11359: ---------------------------------------- Summary: support multiple ssh keys Key: JBIDE-11359 URL: https://issues.jboss.org/browse/JBIDE-11359 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 3.3.0.Beta1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.Beta3 OpenShift added support for multiple ssh keys for a single user account: !add-additional-ssh-key.png! In JBoss Tools we currently only support a single SSH key. It would be nice if we would also support that. We'd have to add this to the client and to the UI. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
7
0 / 0

[JBoss JIRA] (JBIDE-10034) When you try to create the 6th application, error says "could not configure", not mentioning that 5 apps is the maximum

by Andre Dietisheim (Created) (JIRA)

When you try to create the 6th application, error says "could not configure", not mentioning that 5 apps is the maximum ----------------------------------------------------------------------------------------------------------------------- Key: JBIDE-10034 URL: https://issues.jboss.org/browse/JBIDE-10034 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 3.3.0.M4 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 Attachments: cannot-create-6th-app.png In OpenShift Express you can actually only create 5 applications. In the tooling, if you try to create the 6th, the tooling would report you that the 6th app could not be configured. !cannot-create-6th-app.png! It unfortunately does not tell you that there is a limit of 5 applications. We should tell the user that he can only create 5 applications. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

4
6
0 / 0

[JBoss JIRA] (JBIDE-11407) Put egit util tests into their own test feature

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-11407: ---------------------------------------- Summary: Put egit util tests into their own test feature Key: JBIDE-11407 URL: https://issues.jboss.org/browse/JBIDE-11407 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 3.3.0.Beta1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.Beta3 Currently the egit tests are contained within *org.jboss.tools.openshift.express.test.feature*. Even thought the egit utils are in their own feature *org.jboss.tools.openshift.egit.integration.feature*. We should create a new egit tests feature to be consistent. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-10651) Server side update of what is being shown in project examples/tutorials on Central

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-10651: ------------------------------------------- Summary: Server side update of what is being shown in project examples/tutorials on Central Key: JBIDE-10651 URL: https://issues.jboss.org/browse/JBIDE-10651 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Reporter: Max Rydahl Andersen Assignee: Snjezana Peco Priority: Critical Fix For: 3.3.0.Beta1 Need to be controllable on server side what tags/projects are being shown on central. This might all be handled via JBIDE-10461, then all that is left to do is document how this can be controlled/managed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

4
10
0 / 0

[JBoss JIRA] (JBIDE-11257) tooltips in jboss central seem to "linger"

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-11257: ----------------------------------- Summary: tooltips in jboss central seem to "linger" Key: JBIDE-11257 URL: https://issues.jboss.org/browse/JBIDE-11257 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Reporter: Burr Sutter Assignee: Snjezana Peco Attachments: Screen Shot 2012-03-10 at 2.59.23 PM.png, Screen Shot 2012-03-10 at 2.59.34 PM.png With beta1e, I am noticing that the tooltips from JBoss Central's quickstarts tend to "hang around", the solution is to revisit JBoss Central and move the mouse around the quickstarts area, that causes the previous tooltip to close. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

4
11
0 / 0

[JBoss JIRA] (JBIDE-11442) News part of central is sometimes empty (No entries found)

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-11442: ---------------------------------- Summary: News part of central is sometimes empty (No entries found) Key: JBIDE-11442 URL: https://issues.jboss.org/browse/JBIDE-11442 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 3.3.0.Beta2 Reporter: Radim Hopp Assignee: Snjezana Peco Fix For: 3.3.0.Beta3 News part sometimes says "No entries found", because of feedburner content is empty (http://planet.jboss.org/feeds/news). It happens from time to time (can't find any pattern when it is happening). Once I noticed the same happened to Blogs part as well. It usually takes about hour to work again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
3
0 / 0

[JBoss JIRA] (JBIDE-11325) When delete of OpenShift application fails the user is not notified

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-11325: --------------------------------------- Summary: When delete of OpenShift application fails the user is not notified Key: JBIDE-11325 URL: https://issues.jboss.org/browse/JBIDE-11325 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Beta1 Reporter: Lucia Jelinkova Assignee: Xavier Coulon Fix For: 3.3.0.Beta2 When there's an error during the deletion of OpenShift application in OpenShift Console view there is no error message displayed to the user, the error is only logged to Error log. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
4
0 / 0

[JBoss JIRA] (JBIDE-10527) NullPointerException when creating OpenShift server manually

by Lucia Jelinkova (Created) (JIRA)

NullPointerException when creating OpenShift server manually ------------------------------------------------------------ Key: JBIDE-10527 URL: https://issues.jboss.org/browse/JBIDE-10527 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.M5 Reporter: Lucia Jelinkova Assignee: Andre Dietisheim Priority: Critical When I try to create an OpenShift server manually, the server is created successfully but keeps throwing the following NullPointerException every time I click on it. java.lang.NullPointerException at org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.getDelegate(DelegatingServerBehavior.java:58) at org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.canChangeState(DelegatingServerBehavior.java:158) at org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.canStop(DelegatingServerBehavior.java:150) at org.eclipse.wst.server.core.internal.Server.canStop(Server.java:1833) at org.eclipse.wst.server.ui.internal.view.servers.StopAction.accept(StopAction.java:50) at org.eclipse.wst.server.ui.internal.view.servers.AbstractServerAction.selectionChanged(AbstractServerAction.java:85) at org.eclipse.ui.actions.SelectionProviderAction.selectionChanged(SelectionProviderAction.java:143) at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:164) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:162) at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2188) at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1211) at org.eclipse.ui.navigator.CommonViewer.handleSelect(CommonViewer.java:478) at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1241) at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:239) at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:233) at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:403) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

8
32
0 / 0

[JBoss JIRA] (JBIDE-11127) After downloading a runtime all other runtimes in the install locations are added

by Martin Malina (JIRA)

Martin Malina created JBIDE-11127: ------------------------------------- Summary: After downloading a runtime all other runtimes in the install locations are added Key: JBIDE-11127 URL: https://issues.jboss.org/browse/JBIDE-11127 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtime detection Affects Versions: 3.3.0.Beta1 Environment: jbdevstudio-product-universal-5.0.0.v201203010100M-H88-Beta1.jar Reporter: Martin Malina Assignee: Snjezana Peco Fix For: 3.3.0.CR1 When you Download and add a new runtime using Preferences -> JBoss Tools -> JBoss Tools Runtime Detection -> Download it will install not only the newly downloaded runtime but also all other runtimes in the parent directory. This shouldn't happen as the user didn't ask for it. Consider this scenario: 1. ~/runtimes contains a lot of runtimes 2. download as 7.1 and use the default install location ~/ 3. when the downloading finishes not only as 7.1 will be added but also everything inside ~/runtimes This probably happens because after the download JBT calls the search function in the install dir ~/. To fix this issue it could just call the search on ~/$NEW_RUNTIME_DIR . -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

4
9
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 March 2012