May 2009 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-4339) org.jboss.ide.eclipse.as.test.classpath.ProjectRuntimeTest is failing because classpath now includes more entries than before ?

by Max Rydahl Andersen (JIRA)

org.jboss.ide.eclipse.as.test.classpath.ProjectRuntimeTest is failing because classpath now includes more entries than before ? ------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-4339 URL: https://jira.jboss.org/jira/browse/JBIDE-4339 Project: Tools (JBoss Tools) Issue Type: Task Components: Archives Reporter: Max Rydahl Andersen Assignee: Rob Stryker ProjectRuntimeTest is failing, apparently because it does not expect org.eclipse.jdt.launching.JRE_CONTAINER to be there ?! Which sounds a bit weird i must say - how is JRE classpath a surprise ? :) -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-4343) Multiple errors in Seam20XFacetTestSuite* because of missing commons-beanutils.jar

by Max Rydahl Andersen (JIRA)

Multiple errors in Seam20XFacetTestSuite* because of missing commons-beanutils.jar ---------------------------------------------------------------------------------- Key: JBIDE-4343 URL: https://jira.jboss.org/jira/browse/JBIDE-4343 Project: Tools (JBoss Tools) Issue Type: Task Components: Seam Reporter: Max Rydahl Andersen Assignee: Alexey Kazakov Priority: Blocker Fix For: 3.1.0.M1 http://hudson.jboss.org/hudson/view/JBossTools/job/jbosstools-nightly-3.1... has multiple errors that fail because of the same/similar error: Error Message Found additional files ([commons-beanutils.jar] in F/earprj-ear/EarContent at /qa/services/hudson/hudson_workspace/workspace/jbosstools-nightly-3.1.0.Alpha1/jbds-build/3.1.0.M1/200905200002/tests/workspace/earprj-ear/EarContent I assume either the test is faulty or hudson is not configured correctly with the proper seam runtimes ? -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-4341) JstJspAllTests/testJsfJspJbide1813Test failing with missing applicationScope in completions

by Max Rydahl Andersen (JIRA)

JstJspAllTests/testJsfJspJbide1813Test failing with missing applicationScope in completions ------------------------------------------------------------------------------------------- Key: JBIDE-4341 URL: https://jira.jboss.org/jira/browse/JBIDE-4341 Project: Tools (JBoss Tools) Issue Type: Task Components: jsp/jsf/xml source editing Reporter: Max Rydahl Andersen Assignee: Victor Rubezhny Priority: Blocker Fix For: 3.1.0.M1 I guess this has to do with the changed ways of doing completions, but is the functionallity or the test wrong ? http://hudson.jboss.org/hudson/view/JBossTools/job/jbosstools-nightly-3.1... Proposal #{applicationScope} not found! Stacktrace junit.framework.AssertionFailedError: Proposal #{applicationScope} not found! at org.jboss.tools.jst.jsp.test.ca.ContentAssistantTestCase.checkProposals(ContentAssistantTestCase.java:86) at org.jboss.tools.jst.jsp.test.ca.JsfJspJbide1813Test.testJsfJspJbide1813Test(JsfJspJbide1813Test.java:39) -- 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, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-4344) SeamSettingsPreferencesPageTest is failing and is not runnable standalone

by Max Rydahl Andersen (JIRA)

SeamSettingsPreferencesPageTest is failing and is not runnable standalone ------------------------------------------------------------------------- Key: JBIDE-4344 URL: https://jira.jboss.org/jira/browse/JBIDE-4344 Project: Tools (JBoss Tools) Issue Type: Task Components: Seam Reporter: Max Rydahl Andersen Assignee: Alexey Kazakov Fix For: 3.1.0.M1 SeamSettingsPreferencePage is failing with some missed property. http://hudson.jboss.org/hudson/view/JBossTools/job/jbosstools-nightly-3.1... Error Message Model source folder property is not set expected:<[]> but was:<[/TestSeamSettingsPreferencesPage/src]> Stacktrace junit.framework.ComparisonFailure: Model source folder property is not set expected:<[]> but was:<[/TestSeamSettingsPreferencesPage/src]> at org.jboss.tools.seam.ui.test.preferences.SeamSettingsPreferencesPageTest.testSettingsPage(SeamSettingsPreferencesPageTest.java:120) I tried to run the test standalone to see what is causing it but even efter setting the SEAM_1_2 property it fails for me with: junit.framework.AssertionFailedError: TestSeamSettingsPreferencesPage project is not imported. at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertNotNull(Assert.java:217) at org.jboss.tools.seam.ui.test.preferences.SeamSettingsPreferencesPageTest.setUp(SeamSettingsPreferencesPageTest.java:72) Where is that project supposed to be 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

16 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBDS-719) Open On to open the correspondent Seam component is added

by Svetlana mukhina (JIRA)

Open On to open the correspondent Seam component is added --------------------------------------------------------- Key: JBDS-719 URL: https://jira.jboss.org/jira/browse/JBDS-719 Project: Developer Studio Issue Type: Feature Request Components: Doc - Seam Affects Versions: 2.0.0.GA Reporter: Svetlana mukhina Assignee: Olga Chukhutsina Fix For: 2.1.0 mention "Add option (Open On) to open the correspondent Seam component when we have a @In annotation in a field and click on the field name" it in the following sections: 4.2.2. Open Seam Component 7.4.3. OpenOn See the linked task -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBDS-466) Capital letters in sample projects names

by Svetlana mukhina (JIRA)

Capital letters in sample projects names ---------------------------------------- Key: JBDS-466 URL: https://jira.jboss.org/jira/browse/JBDS-466 Project: Developer Studio Issue Type: Task Components: documentation Affects Versions: 1.1.0.GA Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 2.0.0.beta1 There should not be text examples, screens or movies containing project names with capital letters, check all guides and inform others about this. -- 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, 5 months

3
26
0 / 0

[JBoss JIRA] Created: (JBIDE-4340) org.jboss.tools.common.model.test.MetaModelTest is failing because of missing icons

by Max Rydahl Andersen (JIRA)

org.jboss.tools.common.model.test.MetaModelTest is failing because of missing icons ----------------------------------------------------------------------------------- Key: JBIDE-4340 URL: https://jira.jboss.org/jira/browse/JBIDE-4340 Project: Tools (JBoss Tools) Issue Type: Task Components: common Reporter: Max Rydahl Andersen Assignee: Viacheslav Kabanovich Priority: Blocker Fix For: 3.1.0.M1 Not sure what caused it to fail - but it have been failing for ages. Seem like we are missing some images ? or are the test just out of date ? junit.framework.AssertionFailedError: Icons for 5 actions are missing. ActionPath=FaceletTaglibTag:CreateActions/AddSource iconPath=empty ActionPath=FaceletTaglibTag:CreateActions/AddValidator iconPath=empty ActionPath=FaceletTaglibTag:CreateActions/AddComponent iconPath=empty ActionPath=FaceletTaglibTag:CreateActions/AddConverter iconPath=empty ActionPath=FaceletTaglibTag:CreateActions/AddHandler iconPath=empty at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.jboss.tools.common.model.test.MetaModelTest.testActionIcons(MetaModelTest.java:241) 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 junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130) 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.UITestApplication$1.run(UITestApplication.java:114) 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.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.pde.internal.junit.runtime.UITestApplication.start(UITestApplication.java:46) 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

16 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-4338) org.jboss.tools.common.util.test.HttpUtilTest are failing because of NPE when trying to get Proxy Service

by Max Rydahl Andersen (JIRA)

org.jboss.tools.common.util.test.HttpUtilTest are failing because of NPE when trying to get Proxy Service --------------------------------------------------------------------------------------------------------- Key: JBIDE-4338 URL: https://jira.jboss.org/jira/browse/JBIDE-4338 Project: Tools (JBoss Tools) Issue Type: Task Components: common Reporter: Max Rydahl Andersen Assignee: Alexey Kazakov Priority: Blocker Fix For: 3.1.0.M1 The test fails for me locally too, apparently CommonPlugin instance variable is not initialized because it is never been setup to start afaics. Any idea what caused this ? i.e. did we change the startup sequence of plugins or ? I would also expect the instance to be initialized in a start() method and not on the constructor which seems very non-standard way. Last failure: http://hudson.qa.jboss.com/hudson/job/jbosstools-nightly-3.1.0.Alpha1/180... And here is the NPE you can see if you remove the fail and exception handling code java.lang.NullPointerException at org.jboss.tools.common.util.HttpUtil.getProxyService(HttpUtil.java:190) at org.jboss.tools.common.util.HttpUtil.createHttpClient(HttpUtil.java:144) at org.jboss.tools.common.util.test.HttpUtilTest.testCreateHttpClient(HttpUtilTest.java:23) 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 junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130) 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.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-4298) Rename some labels of smooks configuration editor

by Xue Peng (JIRA)

Rename some labels of smooks configuration editor ------------------------------------------------- Key: JBIDE-4298 URL: https://jira.jboss.org/jira/browse/JBIDE-4298 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.1.0.M1 Reporter: Xue Peng Assignee: Xue Peng Priority: Minor Rename some labels of smooks configuration editor. 1,Label of popmenu. 2.Label of TreeViewer 3.Lable of MasterDetail page. -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-4266) Add and option to testBuild to enable/disable eclipse tracing to find out on what point tests have JVM error in ziplib.so

by Denis Golovin (JIRA)

Add and option to testBuild to enable/disable eclipse tracing to find out on what point tests have JVM error in ziplib.so ------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-4266 URL: https://jira.jboss.org/jira/browse/JBIDE-4266 Project: Tools (JBoss Tools) Issue Type: Task Components: Build/Releng Affects Versions: 3.1.0.M1 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 3.1.0.M1 org.eclipse.jdt.core/debug/indexmanager=true org.eclipse.jdt.core//debug/zipaccess=true -- 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, 5 months

3
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2009