February 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-5848) Content Assist doesn't shows proposals for JSF Resource Bundles and image file paths

by Victor Rubezhny (JIRA)

Content Assist doesn't shows proposals for JSF Resource Bundles and image file paths ------------------------------------------------------------------------------------ Key: JBIDE-5848 URL: https://jira.jboss.org/jira/browse/JBIDE-5848 Project: Tools (JBoss Tools) Issue Type: Bug Components: common, jsp/jsf/xml source editing Affects Versions: 3.1.0.CR1 Reporter: Victor Rubezhny Assignee: Alexey Kazakov Fix For: 3.1.0.CR2 The issue is found by JstJspAllTests.testCAForIDTest JUnit TestCase (JBIDE-5844) Steps to reproduce: EXECUTE: Create JSF Facelets KickStart project EXECUTE: Open inputname.xhtml file in JBoss Tools HTML Editor EXECUTE: Find <f:loadBundle /> tag, clear its "basename" attribute value, place text cursor in it (<f:loadBundle basename="|" />) and press Ctrl-Space to invoke CA ASSERT: There must be "resources" CA proposal amount the other propposals (FAILED) EXECUTE: Add "img" folder to WebContent and place some image file into this folder. EXECUTE: Insert <h:graphicImage url="" /> into a valid region of inputname.xhtml file in editor, place text cursor into the value of "url" attribute (url="|") and press Ctrl-Space to invoke CA ASSERT: There must be "/img" folder CA proposal amount the other propposals (FAILED) -- 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

16 years, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-5844) JstJspAllTests.testCAForIDTest fails: Proposal resources not found!

by Nick Boldt (JIRA)

JstJspAllTests.testCAForIDTest fails: Proposal resources not found! ------------------------------------------------------------------- Key: JBIDE-5844 URL: https://jira.jboss.org/jira/browse/JBIDE-5844 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.CR2 Reporter: Nick Boldt Assignee: Max Rydahl Andersen Failed JstJspAllTests.testCAForIDTest Failing for the past 3 builds (Since #153 ) Took 8.6 sec. add description Error Message Proposal resources not found! Stacktrace junit.framework.AssertionFailedError: Proposal resources not found! at org.jboss.tools.jst.jsp.test.ca.ContentAssistantTestCase.checkProposals(ContentAssistantTestCase.java:100) at org.jboss.tools.jst.jsp.test.ca.ContentAssistantTestCase.checkProposals(ContentAssistantTestCase.java:59) at org.jboss.tools.jst.jsp.test.ca.MissingKBBuilderTest.testCAForIDTest(MissingKBBuilderTest.java:34) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206) at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195) 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:3468) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3115) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.test.UITestApplication.runApplication(UITestApplication.java:138) at org.eclipse.test.UITestApplication.run(UITestApplication.java:60) at org.eclipse.test.UITestApplication.start(UITestApplication.java:210) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) 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:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287) at org.eclipse.core.launcher.Main.main(Main.java:34) http://hudson.qa.jboss.com/hudson/view/DevStudio/job/devstudio-nightly-3.... -- 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

16 years, 1 month

4
4
0 / 0

[JBoss JIRA] Created: (JBDS-1095) jboss-esb.xml editor lists are of the same order

by Svetlana mukhina (JIRA)

jboss-esb.xml editor lists are of the same order ------------------------------------------------- Key: JBDS-1095 URL: https://jira.jboss.org/jira/browse/JBDS-1095 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: Doc - ESB Affects Versions: 3.0.0.CR1 Reporter: Svetlana mukhina Assignee: Svetlana mukhina Priority: Minor Fix For: 3.0.0.GA Update the screens -- 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

16 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5729) After installing JBoss Tools, some project types can not be deleted

by David Balažic (JIRA)

After installing JBoss Tools, some project types can not be deleted -------------------------------------------------------------------- Key: JBIDE-5729 URL: https://jira.jboss.org/jira/browse/JBIDE-5729 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.CR1 Environment: Windows XP Professional SP3 java version "1.6.0_17" Java(TM) SE Runtime Environment (build 1.6.0_17-b04) Java HotSpot(TM) Client VM (build 14.3-b01, mixed mode, sharing) Eclipse Java EE 3.5.1 (Galileo SR1) Reporter: David Balažic After installing JBoss Tools*, there is no more a "Delete" item in the context menu of some projects in Project explorer. Example: - an "Enterprise Application Project" has no more a Delete item in its context menu ("Java EE" perspective) Also there is no more a New submeni item in the context menu, noo matter what is clicked: - nothing is selected - a project - a directory folder - a .java file * - Installed today from http://download.jboss.org/jbosstools/updates/development/ -- 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

16 years, 1 month

6
8
0 / 0

[JBoss JIRA] Created: (JBIDE-5868) "New" vanished from context menu in project explorer in the Java EE perspective

by Stephan Kleine (JIRA)

"New" vanished from context menu in project explorer in the Java EE perspective ------------------------------------------------------------------------------- Key: JBIDE-5868 URL: https://jira.jboss.org/jira/browse/JBIDE-5868 Project: Tools (JBoss Tools) Issue Type: Bug Environment: Linux x86_64 Reporter: Stephan Kleine As soon as one installs JBoss Tools the "New" option that is normally shown as the first thing in the context menu in the project explorer view vanishes if one uses the Java EE perspective. It is still there in the Java perspective. I'm currently using Eclipse 3.5 SR1 and the latest from http://download.jboss.org/jbosstools/updates/development/ -- 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

16 years, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5869) Adding "Seam" facet always creates a whole bunch of files

by Stephan Kleine (JIRA)

Adding "Seam" facet always creates a whole bunch of files --------------------------------------------------------- Key: JBIDE-5869 URL: https://jira.jboss.org/jira/browse/JBIDE-5869 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Stephan Kleine As soon as one adds the "Seam" facet to an existing project it always adds a whole bunch of files to the project with no way to prevent this. Don't get me wrong, it's great that you make it easier for people to get started but if one doesn't want those for some reason it is highly annoying having to manually hunt them down to delete them. Therefore please add some "Generate template files" option so one can avoid them being generated and spread all over the project if one doesn't want this. I'm using Eclipse 3.5 SR1 and the latest from http://download.jboss.org/jbosstools/updates/development/ -- 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

16 years, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5469) Unable to Add JSF Capabilities

by Vlado Pakan (JIRA)

Unable to Add JSF Capabilities ------------------------------ Key: JBIDE-5469 URL: https://jira.jboss.org/jira/browse/JBIDE-5469 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.1.0.CR1 Environment: Linux 32 bit, Linux 64 bit Java Sun 1.6 JDK Reporter: Vlado Pakan It's not possible to Add JSF Capabilities to JSF project after they were removed. Steps to reproduce: 1. Create new JSF Project 2. Open Web Project view and Remove JSF Capabilities from JSF Project using popup menu 3. Open Package Explorer and try to Add JSF Capabilities using popup menu JBoss Tools > Add JSF Capabilities. It's not possible because JBoss Tools submenu contains only one disabled menu item with label "Verify". -- 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

16 years, 1 month

6
14
0 / 0

[JBoss JIRA] Created: (JBIDE-5872) VPE throws java.lang.NullPointerException, while editing font-family

by Yahor Radtsevich (JIRA)

VPE throws java.lang.NullPointerException, while editing font-family -------------------------------------------------------------------- Key: JBIDE-5872 URL: https://jira.jboss.org/jira/browse/JBIDE-5872 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.1.0.CR1 Reporter: Yahor Radtsevich Assignee: Maxim Areshkau Priority: Critical Fix For: 3.1.0.CR2 STEPS TO REPRODUCE: 1. Create new HTML file and open it in VPE. 2. Enter the following line in the file: <button style='FONT-FAMILY: "serif">bla bla</button> 3. Delete quote symbol (') after "serif". RESULT: java.lang.NullPointerException is thrown: java.lang.NullPointerException at org.jboss.tools.vpe.editor.toolbar.format.FontNameFormatController.setToolbarItemEnabled(FontNameFormatController.java:92) at org.jboss.tools.vpe.editor.toolbar.format.FormatControllerManager.selectionChanged(FormatControllerManager.java:153) at org.jboss.tools.vpe.editor.toolbar.format.FormatControllerManager.selectionChanged(FormatControllerManager.java:106) at org.jboss.tools.vpe.editor.VpeController.selectionChanged(VpeController.java:2661) at org.eclipse.wst.sse.ui.StructuredTextEditor$5.run(StructuredTextEditor.java:627) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.wst.sse.ui.StructuredTextEditor$StructuredSelectionProvider.fireSelectionChanged(StructuredTextEditor.java:625) at org.eclipse.wst.sse.ui.StructuredTextEditor$StructuredSelectionProvider.handleSelectionChanged(StructuredTextEditor.java:717) at org.eclipse.wst.sse.ui.StructuredTextEditor$3.selectionChanged(StructuredTextEditor.java:593) at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:162) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.runtime.Platform.run(Platform.java:888) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:160) at org.eclipse.jface.text.TextViewer.fireSelectionChanged(TextViewer.java:2714) at org.eclipse.jface.text.TextViewer.selectionChanged(TextViewer.java:2693) at org.eclipse.jface.text.TextViewer$4.widgetSelected(TextViewer.java:1818) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1027) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1012) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:770) at org.eclipse.swt.custom.StyledText.sendSelectionEvent(StyledText.java:7486) at org.eclipse.swt.custom.StyledText.clearSelection(StyledText.java:1706) at org.eclipse.swt.custom.StyledText.setSelection(StyledText.java:8834) at org.eclipse.swt.custom.StyledText.updateSelection(StyledText.java:9472) at org.eclipse.swt.custom.StyledText.handleTextChanged(StyledText.java:6095) at org.eclipse.swt.custom.StyledText$6.textChanged(StyledText.java:5522) at org.eclipse.jface.text.DefaultDocumentAdapter.fireTextChanged(DefaultDocumentAdapter.java:347) at org.eclipse.jface.text.DefaultDocumentAdapter.documentChanged(DefaultDocumentAdapter.java:291) at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument._fireDocumentChanged(BasicStructuredDocument.java:456) at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.fireStructuredDocumentEvent(BasicStructuredDocument.java:1178) at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.internalReplaceText(BasicStructuredDocument.java:1960) at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2415) at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2400) at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$2(JobSafeStructuredDocument.java:1) at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$3.run(JobSafeStructuredDocument.java:137) at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:147) at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replaceText(JobSafeStructuredDocument.java:144) at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replace(BasicStructuredDocument.java:2360) at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$0(JobSafeStructuredDocument.java:1) at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$1.run(JobSafeStructuredDocument.java:88) at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:147) at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replace(JobSafeStructuredDocument.java:95) at org.eclipse.jface.text.DefaultDocumentAdapter.replaceTextRange(DefaultDocumentAdapter.java:248) at org.eclipse.swt.custom.StyledText.modifyContent(StyledText.java:6637) at org.eclipse.swt.custom.StyledText.sendKeyEvent(StyledText.java:7446) at org.eclipse.swt.custom.StyledText.doContent(StyledText.java:2442) at org.eclipse.swt.custom.StyledText.handleKey(StyledText.java:5817) at org.eclipse.swt.custom.StyledText.handleKeyDown(StyledText.java:5842) at org.eclipse.swt.custom.StyledText$7.handleEvent(StyledText.java:5542) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1027) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1012) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1040) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1036) at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1368) at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:4053) at org.eclipse.swt.widgets.Canvas.WM_CHAR(Canvas.java:346) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3946) at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:342) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4619) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2411) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3501) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) 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:368) 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:585) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287) -- 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

16 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5881) VPE doesn't work

by Krasimir Goutcev (JIRA)

VPE doesn't work ----------------- Key: JBIDE-5881 URL: https://jira.jboss.org/jira/browse/JBIDE-5881 Project: Tools (JBoss Tools) Issue Type: Bug Environment: Win Server2003 x64 nightly build 201002182126 Reporter: Krasimir Goutcev After upgrade to nightly build 201002182126 VPE doesn't work see log file -- 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

16 years, 1 month

7
17
0 / 0

[JBoss JIRA] Created: (JBIDE-5238) Redeployment not working after exception during deployment

by Sebastian Scheid (JIRA)

Redeployment not working after exception during deployment ---------------------------------------------------------- Key: JBIDE-5238 URL: https://jira.jboss.org/jira/browse/JBIDE-5238 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.1.0.M4 Environment: Win XP, JDK 1.6.0_16, JBoss 5.1 GA, Seam 2.2.0 GA, Eclipse Galileo Build id: 20090920-1017, JBoss Tools 3.1 M4 Reporter: Sebastian Scheid Assignee: Rob Stryker JBoss has been started from within Eclipse. An ear (Seam-Project) has been added to the server. If an exception occurrs during deployment of that ear, like a syntax error in components.xml or a RuntimeException during initialization of a Seam-Component, the "Touch Descriptors" command in the toolbar has no effect anymore. Any change in the xml-files in WEB-INF like web.xml, component.xml or pages.xml does not result in a redeploy either. The only solution is to restart the Server. -- 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

16 years, 1 month

4
8
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 2010