December 2009 - jbosstools-issues

[JBoss JIRA] Created: (JBDS-754) Externalize English strings in devstudio code

by Sean Flanigan (JIRA)

Externalize English strings in devstudio code --------------------------------------------- Key: JBDS-754 URL: https://jira.jboss.org/jira/browse/JBDS-754 Project: Developer Studio Issue Type: Feature Request Components: ui/branding Affects Versions: 2.0.0.GA Reporter: Sean Flanigan Assignee: Sean Flanigan As in JBIDE-3557, there are some unexternalized strings which need to be pulled out into .properties files, so that they can be translated. -- 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, 6 months

4
9
0 / 0

[JBoss JIRA] Created: (JBDS-587) Need to translate Help/About text including copyright statement

by Sean Flanigan (JIRA)

Need to translate Help/About text including copyright statement --------------------------------------------------------------- Key: JBDS-587 URL: https://jira.jboss.org/jira/browse/JBDS-587 Project: Developer Studio Issue Type: Feature Request Components: Build Affects Versions: 2.0.0.cr1 Reporter: Sean Flanigan Help/About JBoss Developer Studio shows the version/copyright information for JBDS. This text looks similar to /com.jboss.jbds.product/plugin.properties but is actually overwritten/expanded from releng/org.jboss.ide.eclipse.releng/builders/product/product.properties during the build. The problem is, if we create a translation fragment plugin for com.jboss.jbds.product, the translators will translate the obsolete information in /com.jboss.jbds.product/plugin.properties, and when a langpack is installed, the up-to-date information will be replaced by obsolete information. We need to work out how to handle this better, preferably keeping the translatable text somewhere in com.jboss.jbds.product, not in releng. Perhaps we could do something with /com.jboss.jbds.product/about.mappings / about.ini? Ref: http://help.eclipse.org/stable/index.jsp?topic=/org.eclipse.platform.doc.... -- 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, 6 months

6
28
0 / 0

[JBoss JIRA] Created: (JBIDE-4177) Seam Booking project example errors.

by Aliaksey Nis (JIRA)

Seam Booking project example errors. ------------------------------------ Key: JBIDE-4177 URL: https://jira.jboss.org/jira/browse/JBIDE-4177 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 3.1.0 Environment: WindowsXP SP2 JBoss Tools Version: 3.1.0 Build id: JBossTools-ALL-win32-3.1.0.Alpha1-N200904090001-H90 JRE 1.5_08 Reporter: Aliaksey Nis Priority: Minor EXECUTE: Import Seam Booking example project. EXECUTE: Open Problems view. FAILURE: 3 errors shown here. 1. The element type "INPUT" must be terminated by the matching end-tag "</INPUT>". File: introExp.html Folder: booking/WebContent/exp Line: line 22 2. The element type "INPUT" must be terminated by the matching end-tag "</INPUT>". File: workspaceExp.html Folder: booking/WebContent/exp Line: line 22 3. The entity name must immediately follow the '&' in the entity reference. File: mainExp.html Folder: booking/WebContent/exp Line: line 94 Example project must be correctly imported. -- 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, 6 months

4
8
0 / 0

[JBoss JIRA] Created: (JBDS-564) Internationalise Dev Studio installer

by Sean Flanigan (JIRA)

Internationalise Dev Studio installer ------------------------------------- Key: JBDS-564 URL: https://jira.jboss.org/jira/browse/JBDS-564 Project: Developer Studio Issue Type: Feature Request Components: installer Reporter: Sean Flanigan Assignee: Sean Flanigan Link from Denis Golovin: http://izpack.org/documentation/installation-files.html#internationalizat... We should probably try to reuse some of the tooling developed for the JEMS installer by Caius Chance. See http://www.jboss.org/community/docs/DOC-10872 and http://anonsvn.jboss.org/repos/installer/jems-installer/branches/Branch_M... -- 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, 6 months

3
10
0 / 0

[JBoss JIRA] Created: (JBDS-1034) ESB Node Properties for Input/Output variables grows larger than panel when panel is resized.

by Aaron Pestel (JIRA)

ESB Node Properties for Input/Output variables grows larger than panel when panel is resized. --------------------------------------------------------------------------------------------- Key: JBDS-1034 URL: https://jira.jboss.org/jira/browse/JBDS-1034 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 3.0.0.M4 Environment: JBDS 3.0 M4 Reporter: Aaron Pestel Priority: Minor To reproduce: 1.) Drag an ESB Service node on jBPM Diagram Pallette 2.) Click on (select) the new ESB Service node 3.) Select the Properties view tab 4.) Click the ESB subtab of the ESB Properties panel 5.) Click the "Input" subsubtab of the ESB subtab of the ESB Properties panel 6.) Grab the left edge of the "Properties" panel and move it to the left (increasing the width of the Properties panel) 7.) Note that the ESB Input sub panel grows wide faster than its Properties panel container such that you can no longer see the "Add" button in the ESB Input sub panel without scrolling. -- 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, 6 months

7
23
0 / 0

[JBoss JIRA] Created: (JBIDE-4717) JBoss Portlet facet is available only when there is no runtime selected

by Denis Golovin (JIRA)

JBoss Portlet facet is available only when there is no runtime selected ----------------------------------------------------------------------- Key: JBIDE-4717 URL: https://jira.jboss.org/jira/browse/JBIDE-4717 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.1.GA Reporter: Denis Golovin Assignee: Snjezana Peco Fix For: 3.0.2.GA -- 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, 6 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-4331) Exception when adding ESB library to class path

by Vincent Girard-Reydet (JIRA)

Exception when adding ESB library to class path ----------------------------------------------- Key: JBIDE-4331 URL: https://jira.jboss.org/jira/browse/JBIDE-4331 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.0.1.GA, 3.0.0.GA Environment: eclipse.buildId=M20090211-1700 java.version=1.6.0_12 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=fr_FR Command-line arguments: -os win32 -ws win32 -arch x86 -clean Windows XP SP2 Reporter: Vincent Girard-Reydet Attachments: details.log When I want to add a ESB library to the buildpath of a ESB project (right-click on project -> Properties... -> Java Build Path -> Add Library... -> Jboss ESB library ), nothing happens after clicking on the "Next" button. When switching to the PDE development perspective, I see a lot of errors, some of them beeing related to JBossESB tools. I must precise that the ESB libraries are correctly added to the project's build path when I create a new ESB project. But if I want to change the ESB library, or add a dependency to an ESB library to any project (including non-ESB projects), I got systematically this exception. Please see the log in attachment for the full Eclipse log. I captured it right after the exception (got the problem, switched to the PDE perspective and exported the log). -- 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, 6 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-5078) Studio does not start correctly afer VPE editor was opened in previous session

by Daniel Azarov (JIRA)

Studio does not start correctly afer VPE editor was opened in previous session ------------------------------------------------------------------------------ Key: JBIDE-5078 URL: https://jira.jboss.org/jira/browse/JBIDE-5078 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.1.0.M3 Reporter: Daniel Azarov Priority: Critical Testcase: 1. Open Studio with new workspace 2. Create jsf kick start project 3. Open WebContent/index.jsp 4. Close Studio 5. Open Studio again FAIL: org.eclipse.swt.SWTError: No more handles [Could not detect registered XULRunner to use] at org.eclipse.swt.SWT.error(SWT.java:3910) at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:471) at org.eclipse.swt.browser.Browser.<init>(Browser.java:119) at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.<init>(XulRunnerBrowser.java:87) at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.<init>(XulRunnerEditor.java:135) at org.jboss.tools.vpe.editor.mozilla.MozillaEditor$10.<init>(MozillaEditor.java:521) at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.createPartControl(MozillaEditor.java:521) at org.jboss.tools.vpe.editor.VpeEditorPart.createVisualEditor(VpeEditorPart.java:911) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:210) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.createPages(JSPMultiPageEditor.java:400) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart.createPartControl(JSPMultiPageEditorPart.java:125) at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:662) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:462) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595) at org.eclipse.ui.internal.EditorAreaHelper.setVisibleEditor(EditorAreaHelper.java:271) at org.eclipse.ui.internal.EditorManager.setVisibleEditor(EditorManager.java:1417) at org.eclipse.ui.internal.EditorManager$5.runWithException(EditorManager.java:942) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) 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:3855) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3476) at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803) at org.eclipse.ui.internal.Workbench$28.runWithException(Workbench.java:1384) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) 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:3855) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3476) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2316) 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(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) 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

15 years, 6 months

9
34
0 / 0

[JBoss JIRA] Created: (JBIDE-3968) Create unittests for dali integration

by Max Rydahl Andersen (JIRA)

Create unittests for dali integration ------------------------------------- Key: JBIDE-3968 URL: https://jira.jboss.org/jira/browse/JBIDE-3968 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Reporter: Max Rydahl Andersen Assignee: Dmitry Geraskov Priority: Blocker Fix For: 3.0.1.GA, 3.1.0 While fixing JBIDE-3960 I wanted to verify my fixes did not break anything but I had no way of verifying this except tiny manual tests to be ready for GA. I also believe if we had had any trivial tests they would had prevented JBIDE-3960 since it would have showed up instantly. We need to add tests for the Dali integration, especially when we have funky code like reflection for Dali 2.1 and Dali 2.0 -- 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, 6 months

4
18
0 / 0

[JBoss JIRA] Created: (JBIDE-3337) Exception is occured when delete Seam Ear web project

by Anton Klimkovich (JIRA)

Exception is occured when delete Seam Ear web project ----------------------------------------------------- Key: JBIDE-3337 URL: https://jira.jboss.org/jira/browse/JBIDE-3337 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.0.0.cr1 Reporter: Anton Klimkovich Attachments: exception.txt EXECUTE: Create seam EAR web project EXECUTE: Select all projects in Package Explorer View EXECUTE: Delete with content from workspace FAILURE: Exception is occured after deleting. -- 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, 6 months

5
18
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 December 2009