January 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-1894) The readme.txt once installed contains a broken link to the release notes

by Vlado Pakan (Created) (JIRA)

The readme.txt once installed contains a broken link to the release notes ------------------------------------------------------------------------- Key: JBDS-1894 URL: https://issues.jboss.org/browse/JBDS-1894 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: documentation Affects Versions: 4.1.0.CR3 Environment: JBoss Developer Studio 4.1 - I only tried the x64 Linux standalone version but I presume this may be present in other installations. Reporter: Vlado Pakan Assignee: Nick Boldt Fix For: 4.1.1.M2, 5.0.0.M4 Once installed the readme.txt found the installation directory contains a link to the release notes: http://docs.redhat.com/docs/en-US/JBoss_Developer_Studio/4.0/html-single/... Firstly it's the wrong version and secondly the link doesn't exist. It should be: http://docs.redhat.com/docs/en-US/JBoss_Developer_Studio/4.1/html-single/... -- 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

14 years, 1 month

6
5
0 / 0

[JBoss JIRA] Created: (JBDS-1508) Calculate properly font size when displaying version information on Splashscreen

by Vlado Pakan (JIRA)

Calculate properly font size when displaying version information on Splashscreen -------------------------------------------------------------------------------- Key: JBDS-1508 URL: https://issues.jboss.org/browse/JBDS-1508 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: ui/branding Affects Versions: 4.0.0.CR1 Environment: JBDS 4.0.0.v20110116-1048-H515-CR1 Reporter: Vlado Pakan Priority: Minor Currently is font size of version text displayed on JBDS splash screen hardcoded. It's fine until version text is not too long. When complete build id is displayed ( when property -DSHOW_BUILDID_ON_STARTUP=true is specified when starting eclipse) than version text is too long and is displayed only partially. Logic how to calculate displayed text dimensions is already in source code so we need to find out maximal rectangle which can version text occupy and upon that dimensions properly calculate font size used for version text. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (JBIDE-9681) Undo and Redo menu items are disabled for web page edited via VPE

by Vlado Pakan (JIRA)

Undo and Redo menu items are disabled for web page edited via VPE ----------------------------------------------------------------- Key: JBIDE-9681 URL: https://issues.jboss.org/browse/JBIDE-9681 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.3.0.M3 Environment: jbdevstudio-product-macosx-cocoa-5.0.0.v201109071858R-H28-M3. Reporter: Vlado Pakan Assignee: Yahor Radtsevich Fix For: 3.3.0.M4 Open some web page in VPE and make some changes. Open edit menu. Undo and Redo menu items are disabled. User cannot choose them. Undo shortcut (Command+Z) is working. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
8
0 / 0

[JBoss JIRA] (JBIDE-10674) add EAP 6 to test requirements for JBT/JBDS

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-10674: ---------------------------------- Summary: add EAP 6 to test requirements for JBT/JBDS Key: JBIDE-10674 URL: https://issues.jboss.org/browse/JBIDE-10674 Project: Tools (JBoss Tools) Issue Type: Bug Components: testing Affects Versions: 3.3.0.Beta1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.3.0.Beta1 EAP 6.0.0 DR 11 is now available and should be used for integration testing in JBT/JBDS. -- 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

14 years, 1 month

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-9674) Issues with Support for special and non-ASCII characters to the Externalize Strings Wizard for JSP

by Max Rydahl Andersen (JIRA)

Issues with Support for special and non-ASCII characters to the Externalize Strings Wizard for JSP -------------------------------------------------------------------------------------------------- Key: JBIDE-9674 URL: https://issues.jboss.org/browse/JBIDE-9674 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core Affects Versions: 3.3.0.M2 Environment: Linux 32bit, Sun JDK 1.6.0_25, jbdevstudio-product-linux-gtk-5.0.0.v201106172137N-H681-M2. Reporter: Vlado Pakan Assignee: Denis Maliarevich Fix For: 3.3.0.M3 1. Create JSF kick start project 2. Open hello.jsp page 3. Insert "Plain" text as shown on picture below and choose Externalize selected string toolbar button In the Externalize String dialog is set text "Plain" as Property value but together with special characters <EOL> !externalizestringdialog.png! 4. Choose next>, next>, OK. (Use default values) hello.jsp page look like this. <EOL> characters around "Plain" text were removed/replaced with reference to .properties file: !externalizestringresult.png! hello.properties has wrong contnent: !propertiesfile.png! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

4
10
0 / 0

[JBoss JIRA] (JBIDE-10689) HTML 5 Project is not properly rendered via internal eclipse browser

by Vlado Pakan (JIRA)

Vlado Pakan created JBIDE-10689: ----------------------------------- Summary: HTML 5 Project is not properly rendered via internal eclipse browser Key: JBIDE-10689 URL: https://issues.jboss.org/browse/JBIDE-10689 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.3.0.Beta1 Environment: JBT 2012-01-18_10-32-21-H4144, Linux 32 bit, Java Sun 1.6.0_30 Reporter: Vlado Pakan 1. Open JBoss Central 2. Create new HTTP 5 project 3. Run this project on server ERROR: Page is not properly rendered in Eclipse Browser. See attached screenshot. When new user is registered no validation errors are displayed and when valid data are specified and "Register" button is chosen new user is saved but not displayed in Members List until page is refreshed. -- 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

14 years, 1 month

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-9059) Display Error Message in Dialog Window when using VPE with Java 5

by Vlado Pakan (JIRA)

Display Error Message in Dialog Window when using VPE with Java 5 ----------------------------------------------------------------- Key: JBIDE-9059 URL: https://issues.jboss.org/browse/JBIDE-9059 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core Affects Versions: 3.2.1.CR1 Environment: jbdevstudio-product-eap-linux-gtk-4.1.0.v201105312352R-H528-CR1 Reporter: Vlado Pakan Assignee: Yahor Radtsevich Priority: Minor Fix For: 3.2.1.CR2 It would be nice to display error message when VPE is used with Java v.5 not just in Error Log but also to dialog window with check box "Do not show this error again". It's more informative for user to see the reason why Visual part of VPE editor is not shown in dialog window then just in Error Log view. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

6
20
0 / 0

[JBoss JIRA] (JBIDE-10701) NPE in JaxrsMetamodelBuilder

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-10701: ----------------------------------- Summary: NPE in JaxrsMetamodelBuilder Key: JBIDE-10701 URL: https://issues.jboss.org/browse/JBIDE-10701 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.3.0.Beta1 Reporter: Fred Bricon Assignee: Xavier Coulon While running m2e-wtp test suite, I got a failure caused by {noformat} org.eclipse.core.internal.resources.ResourceException: Errors occurred during the build. at org.eclipse.core.internal.resources.Project$1.run(Project.java:620) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.core.internal.resources.Project.internalBuild(Project.java:597) at org.eclipse.core.internal.resources.Project.build(Project.java:114) at org.maven.ide.eclipse.wtp.WTPProjectConfiguratorTest.testMECLIPSEWTP162_UpdateWebFacet(WTPProjectConfiguratorTest.java:1679) 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 junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:243) at junit.framework.TestSuite.run(TestSuite.java:238) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner.main(RemotePluginTestRunner.java:62) at org.eclipse.pde.internal.junit.runtime.PlatformUITestHarness$1.run(PlatformUITestHarness.java:47) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4140) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757) 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.pde.internal.junit.runtime.NonUIThreadTestApplication.runApp(NonUIThreadTestApplication.java:54) at org.eclipse.pde.internal.junit.runtime.UITestApplication.runApp(UITestApplication.java:41) at org.eclipse.pde.internal.junit.runtime.NonUIThreadTestApplication.start(NonUIThreadTestApplication.java:48) 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) Contains: Errors running builder 'JAX-RS Builder' on project 'updatefacets'. java.lang.NullPointerException at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveTypeHierarchy(JdtUtils.java:456) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessor.processApplicationChangesOnWebxmlAdditionOrChange(ResourceChangedProcessor.java:205) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessor.processEvent(ResourceChangedProcessor.java:189) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessor.processEntireProject(ResourceChangedProcessor.java:109) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessor.processAffectedResources(ResourceChangedProcessor.java:80) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelBuilder.build(JaxrsMetamodelBuilder.java:124) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelBuilder.build(JaxrsMetamodelBuilder.java:84) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:394) at org.eclipse.core.internal.resources.Project$1.run(Project.java:618) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.core.internal.resources.Project.internalBuild(Project.java:597) at org.eclipse.core.internal.resources.Project.build(Project.java:114) at org.maven.ide.eclipse.wtp.WTPProjectConfiguratorTest.testMECLIPSEWTP162_UpdateWebFacet(WTPProjectConfiguratorTest.java:1679) 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 junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:243) at junit.framework.TestSuite.run(TestSuite.java:238) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner.main(RemotePluginTestRunner.java:62) at org.eclipse.pde.internal.junit.runtime.PlatformUITestHarness$1.run(PlatformUITestHarness.java:47) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4140) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757) 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.pde.internal.junit.runtime.NonUIThreadTestApplication.runApp(NonUIThreadTestApplication.java:54) at org.eclipse.pde.internal.junit.runtime.UITestApplication.runApp(UITestApplication.java:41) at org.eclipse.pde.internal.junit.runtime.NonUIThreadTestApplication.start(NonUIThreadTestApplication.java:48) 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) {noformat} Test project is available under https://github.com/sonatype/m2eclipse-wtp/tree/master/org.maven.ide.eclip... -- 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

14 years, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7361) Seam toolbar items are showing up in the Teiid toolbar

by Paul Nittel (JIRA)

Seam toolbar items are showing up in the Teiid toolbar ------------------------------------------------------ Key: JBIDE-7361 URL: https://jira.jboss.org/browse/JBIDE-7361 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: LATER Environment: Fedora 12, JBDS 4.0.0 H52 with EDS Reporter: Paul Nittel Assignee: Alexey Kazakov Attachments: Screenshot-SeamTools.png I was inspecting the toolbar to test actions when I noticed that there was no "Find Model Object" button. I did find the "Open Seam Component" and "Open Spring Bean" buttons, but I'm in the Teiid perspective. Even with the Seam perspective closed, there toolbar contains these buttons. Screenshot will be attached. -- 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

14 years, 1 month

8
20
0 / 0

[JBoss JIRA] (JBIDE-10741) Rename named bean action does not look into EL occurences in Java sources

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-10741: --------------------------------------------- Summary: Rename named bean action does not look into EL occurences in Java sources Key: JBIDE-10741 URL: https://issues.jboss.org/browse/JBIDE-10741 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI Affects Versions: 3.3.0.M5 Reporter: Viacheslav Kabanovich Assignee: Daniel Azarov Fix For: 3.3.0.Beta1 EXECUTE: Create class bean {code} public class MyBeanClass { @Produces @Named("name") String s; String s1 = "#{name.charAt(0)}"; } {code} EXECUTE: Call 'Rename "name" named bean'. ASSERT: EL occurance in field 's1' is properly modified. -- 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

14 years, 1 month

3
3
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 2012