September 2011 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-9564) Errors in CDICoreValidator when editing Java during validation of previous saved state.

by Viacheslav Kabanovich (JIRA)

Errors in CDICoreValidator when editing Java during validation of previous saved state. --------------------------------------------------------------------------------------- Key: JBIDE-9564 URL: https://issues.jboss.org/browse/JBIDE-9564 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi Affects Versions: 3.3.0.M2 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M3 Now Java Model updates on the fly at source editing, whereas CDI validator works with CDI model built with the last saved state. That means that some objects of Java model stored in CDI model may get obsolete while validation is in progress. One of possible cases: EXECUTE: Add producer to a bean {code} @Produces String getName(String s) { return null; } {code} EXECUTE: Select and delete argument 'String s'. EXECUTE: Use Ctrl+Z Ctrl+S Ctrl+Y Ctrl+S several times. FAILURE: Java Model Exception 'getName(String) ... does not exist'. Proposed fix. As we will keep to updating CDI model during build of last saved state, CDI model objects need to be able to answer if they exist or not, and validator and other clients should check existence before accessing the object. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-9337) AS7: implement proper lifecycle for as7 service

by Andre Dietisheim (JIRA)

AS7: implement proper lifecycle for as7 service ------------------------------------------------ Key: JBIDE-9337 URL: https://issues.jboss.org/browse/JBIDE-9337 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M3 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M3 The current implementation creates jboss7 management service trackers without disposing them properly. I have to correct this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9373) EL code completion doesn't work for parameterized collections in case of a few dependent projects.

by Alexey Kazakov (JIRA)

EL code completion doesn't work for parameterized collections in case of a few dependent projects. -------------------------------------------------------------------------------------------------- Key: JBIDE-9373 URL: https://issues.jboss.org/browse/JBIDE-9373 Project: Tools (JBoss Tools) Issue Type: Bug Components: common Affects Versions: 3.3.0.M2 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.3.0.M3 EXECUTE: Import weld examples as maven projects. EXECUTE: Open history.xhtml from weld-jsf-pastcode project. EXECUTE: Find <h:outputText id="datetime" value="#{codeFragment.datetime}"> in line 32 EXECUTE: Ctrl+Space on #{codeFragment.| FAILURE: There are no datetime, id and other proposals in the list. The problem is in our TypeInfoCollector which uses a wrong Java project to resolve types of variables if the EL is used in a java project which depends on another java project. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (JBDS-1639) SpringIDE 2.6 dependencies missing from JBDS target, feature, and product definitions

by Nick Boldt (JIRA)

SpringIDE 2.6 dependencies missing from JBDS target, feature, and product definitions ------------------------------------------------------------------------------------- Key: JBDS-1639 URL: https://issues.jboss.org/browse/JBDS-1639 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: 3rdPartyDependencies, Build Affects Versions: 5.0.0.M1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 5.0.0.M1 [INFO] [Software being installed: com.jboss.jbds.springide.feature.feature.group 1.0.1.qualifier, Missing requirement: org.springframework.ide.eclipse.security.feature.feature.group 2.5.1.201011101000-RELEASE requires ' org.apache.commons.codec [1.3.0.v20100518-1140]' but it could not be found, Cannot satisfy dependency: com.jboss.jbds.springide.feature.feature.group 1.0.1.qualifier depends on: org.springframework.ide.eclipse.security.feature.feature.group [2.5.1,3.0.0)] http://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/devstudio-5.0_... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-9533) CDI validation throws exceptions when project is deleted while it runs.

by Viacheslav Kabanovich (JIRA)

CDI validation throws exceptions when project is deleted while it runs. ----------------------------------------------------------------------- Key: JBIDE-9533 URL: https://issues.jboss.org/browse/JBIDE-9533 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi Affects Versions: 3.3.0.M2 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M3 That happens in automatic tests, where creating/building/deleting projects happens many times. Testing is ensured by DependentProjectTest.testCleanDependentProject. There should be no NullPointerExceptions at accessing type with getResource().getFullPath(). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-9451) CDI validation doesn't work for dependent projects.

by Alexey Kazakov (JIRA)

CDI validation doesn't work for dependent projects. --------------------------------------------------- Key: JBIDE-9451 URL: https://issues.jboss.org/browse/JBIDE-9451 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi Affects Versions: 3.3.0.M3 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Priority: Critical Fix For: 3.3.0.M3 EXECUTE: Create two CDI projects: project A and project B. Project A should be added into project B classpath as a dependency. EXECUTE: Close the eclipse. Re-open it. EXECUTE: Change anything in project A to trigger its builders. FAILURE: The following error is thrown in Eclipse log: "Trying to validate P/CDITest2 but CDI Tools model for the project is not built." -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-9289) CDI model should scan all web content folders

by Viacheslav Kabanovich (JIRA)

CDI model should scan all web content folders --------------------------------------------- Key: JBIDE-9289 URL: https://issues.jboss.org/browse/JBIDE-9289 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.3.0.M2 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M3 Web root component in Eclipse can have several underlying resources. At present, model/builder take only 'primary' resource. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-9369) AS7: remote server state is not detected correctly

by Andre Dietisheim (JIRA)

AS7: remote server state is not detected correctly -------------------------------------------------- Key: JBIDE-9369 URL: https://issues.jboss.org/browse/JBIDE-9369 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M3 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9586) AS Testsuite is failing on hudson

by Andre Dietisheim (JIRA)

AS Testsuite is failing on hudson --------------------------------- Key: JBIDE-9586 URL: https://issues.jboss.org/browse/JBIDE-9586 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M3 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M3 ------------------------------------------------------------------------------- Test set: org.jboss.ide.eclipse.as.internal.management.as7.tests.JBossManagementServiceTest ------------------------------------------------------------------------------- Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.097 sec <<< FAILURE! serviceIsReachable(org.jboss.ide.eclipse.as.internal.management.as7.tests.JBossManagementServiceTest) Time elapsed: 0.088 sec <<< FAILURE! java.lang.AssertionError: at org.junit.Assert.fail(Assert.java:91) at org.junit.Assert.assertTrue(Assert.java:43) at org.junit.Assert.assertNotNull(Assert.java:524) at org.junit.Assert.assertNotNull(Assert.java:535) at org.jboss.ide.eclipse.as.internal.management.as7.tests.JBossManagementServiceTest.serviceIsReachable(JBossManagementServiceTest.java:48) 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) 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.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:72) at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) 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:3563) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212) 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.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:114) at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) 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) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-9137) enable org.jboss.ide.eclipse.as.management.as7.tests in build

by Nick Boldt (JIRA)

enable org.jboss.ide.eclipse.as.management.as7.tests in build ------------------------------------------------------------- Key: JBIDE-9137 URL: https://issues.jboss.org/browse/JBIDE-9137 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS, testing Affects Versions: 3.3.0.M2 Reporter: Nick Boldt Assignee: Rob Stryker Now that ~/trunk/as/plugins/org.jboss.ide.eclipse.as.management.as7 is added to the build and contained in a feature, shouldn't the accompanying tests be added to the AS job, too? See: http://anonsvn.jboss.org/repos/jbosstools/trunk/as/tests/org.jboss.ide.ec... http://anonsvn.jboss.org/repos/jbosstools/trunk/as/tests/pom.xml http://anonsvn.jboss.org/repos/jbosstools/trunk/as/features/org.jboss.ide... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
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 September 2011