January 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBIDE-8086) Usage Preference Page name is missing

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8086?page=com.atlassian.jira.plugin... ] Denis Golovin updated JBIDE-8086: --------------------------------- Attachment: screenshot38.png > Usage Preference Page name is missing > ------------------------------------- > > Key: JBIDE-8086 > URL: https://issues.jboss.org/browse/JBIDE-8086 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: usage > Affects Versions: 3.2.0.CR1 > Environment: Linux, gtk, x86 > Reporter: Denis Golovin > Fix For: 3.2.0.CR1 > > Attachments: screenshot38.png > > > 1. EXEC: nstall JBossAS component into Classic Eclipse SDK from nightly update site > 2. EXEC: Open Preferences Dialog > 3. ASSERT: Preferences Page for Usage is present > Now it says %page.name (look at attached screenshot) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-7777) NPE when editing a cloud

by Andre Dietisheim (JIRA)

NPE when editing a cloud ------------------------ Key: JBIDE-7777 URL: https://jira.jboss.org/browse/JBIDE-7777 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.Beta2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.CR1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7715) Provide common super class for NewConnectionWizard and EditConnectionWizard

by Andre Dietisheim (JIRA)

Provide common super class for NewConnectionWizard and EditConnectionWizard --------------------------------------------------------------------------- Key: JBIDE-7715 URL: https://jira.jboss.org/browse/JBIDE-7715 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.Beta2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.Beta2 The current implementation has duplicate code for NewConnectionWizard and EditConnectionWizard. A common superclass shall be provided to remove duplicate code (and bug proliferation) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBDS-1490) JBDS 4 icon in ctrl+tab is of a low resolution

by Max Andersen (JIRA)

JBDS 4 icon in ctrl+tab is of a low resolution ---------------------------------------------- Key: JBDS-1490 URL: https://issues.jboss.org/browse/JBDS-1490 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: ui/branding Reporter: Max Andersen Assignee: Denis Golovin Fix For: 4.0.0.CR1, 4.0.x Can't take a snapshot but it looks like the resolution used for the icon in the Ctrl+Tab on OSX is of a very low resolution. We had similar issue in the previous JBDS builds but it got fixed. Maybe this is a problem on all OS's ? not just OSX ? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7773) Behaviour differences in two different "Launch Instance" actions / wizards

by Rob Stryker (JIRA)

Behaviour differences in two different "Launch Instance" actions / wizards -------------------------------------------------------------------------- Key: JBIDE-7773 URL: https://jira.jboss.org/browse/JBIDE-7773 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.Beta2 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.2.0.CR1 Depending on where you enter from, the wizard looks different and has different behaviour. Specifically, the recent fix for the 10 second delay only affected one entry point and not both due to the two separate classes being used. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5661) JSTL functions (fn:*) are not supported in JBoss Tools Palette

by Oleg Varaksin (JIRA)

JSTL functions (fn:*) are not supported in JBoss Tools Palette -------------------------------------------------------------- Key: JBIDE-5661 URL: https://jira.jboss.org/jira/browse/JBIDE-5661 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.CR1 Environment: Eclipse 3.5 and higher, JBoss Tools 3.1.0.CR1 Reporter: Oleg Varaksin JSTL functions (namespace "fn") are not supported in JBoss Tools Palette. After adding (e.g. per drag-and-drop) appears an empty panel. See screenshot -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-7184) Refresh is normally a context menu action in Eclipse

by Pete Muir (JIRA)

Refresh is normally a context menu action in Eclipse ---------------------------------------------------- Key: JBIDE-7184 URL: https://jira.jboss.org/browse/JBIDE-7184 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.M2 Reporter: Pete Muir Normally refresh is called by right clicking on an artifact (e.g. a folder) and choosing refresh, not from the drop down menu on the top right of the panel. It's very counterintuitive having it up there, it should be available on all folders views (and I would argue not in that menu at all) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
22
0 / 0

[JBoss JIRA] Created: (JBIDE-7564) org.jboss.tools.jsf.ui.test.AddJSFCapabilitiesTest JUnit Test breaks the other tests execution

by Victor Rubezhny (JIRA)

org.jboss.tools.jsf.ui.test.AddJSFCapabilitiesTest JUnit Test breaks the other tests execution ---------------------------------------------------------------------------------------------- Key: JBIDE-7564 URL: https://jira.jboss.org/browse/JBIDE-7564 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF, testing Affects Versions: 3.2.0.Beta1 Reporter: Victor Rubezhny Assignee: Denis Golovin Fix For: 3.2.0.Beta2 While executing the AddJSFCapabilitiesTest the "Open Perspective" dialog appears and test waits for the user to answer. In tycho-build this results in breaking by time-out for the test. All the tests that are to be started after this test fail in their initialization. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-7573) TestWizardsProject failure

by Alexey Kazakov (JIRA)

TestWizardsProject failure -------------------------- Key: JBIDE-7573 URL: https://jira.jboss.org/browse/JBIDE-7573 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.2.0.Beta2 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.2.0.CR1 Tests run: 46, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 832.521 sec <<< FAILURE! JSF UI tests(org.jboss.tools.jsf.ui.test.TestWizardsProject) Time elapsed: 0.288 sec <<< ERROR! org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTException: Widget is disposed) at org.eclipse.swt.SWT.error(SWT.java:4083) at org.eclipse.swt.SWT.error(SWT.java:3998) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:137) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3515) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3164) at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:61) at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:38) at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:27) at org.jboss.tools.test.util.ProjectImportTestSetup.tearDown(ProjectImportTestSetup.java:83) at junit.extensions.TestSetup$1.protect(TestSetup.java:24) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.extensions.TestSetup.run(TestSetup.java:27) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at org.codehaus.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:75) at org.codehaus.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:25) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3515) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3164) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.codehaus.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:21) at org.codehaus.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:109) at org.codehaus.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:27) 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:369) 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:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) Caused by: org.eclipse.swt.SWTException: Widget is disposed at org.eclipse.swt.SWT.error(SWT.java:4083) at org.eclipse.swt.SWT.error(SWT.java:3998) at org.eclipse.swt.SWT.error(SWT.java:3969) at org.eclipse.swt.widgets.Widget.error(Widget.java:466) at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:403) at org.eclipse.swt.widgets.Table.getSelectionIndex(Table.java:1687) at org.jboss.tools.common.model.ui.objecteditor.XTable.getSelectionIndex(XTable.java:219) at org.jboss.tools.common.model.ui.objecteditor.XChildrenEditor.setObject(XChildrenEditor.java:145) at org.jboss.tools.jsf.ui.preferences.JSFCapabilitiesPreferencesPage.capabilitySelectionChanged(JSFCapabilitiesPreferencesPage.java:177) at org.jboss.tools.jsf.ui.preferences.JSFCapabilitiesPreferencesPage.access$0(JSFCapabilitiesPreferencesPage.java:175) at org.jboss.tools.jsf.ui.preferences.JSFCapabilitiesPreferencesPage$1.run(JSFCapabilitiesPreferencesPage.java:90) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) ... 44 more Results : Tests in error: JSF UI tests(org.jboss.tools.jsf.ui.test.TestWizardsProject) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7592) Cloud View: should inform user if authentication fails

by Andre Dietisheim (JIRA)

Cloud View: should inform user if authentication fails ------------------------------------------------------ Key: JBIDE-7592 URL: https://jira.jboss.org/browse/JBIDE-7592 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.Beta2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.CR1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
2
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 January 2011