May 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-8148) New Connection wizard: blocks UI when you hit "Finish"

by Andre Dietisheim (JIRA)

New Connection wizard: blocks UI when you hit "Finish" ------------------------------------------------------ Key: JBIDE-8148 URL: https://issues.jboss.org/browse/JBIDE-8148 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.CR1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.1 If you create a new cloud with the "New cloud connection" wizard, enter all settings and hit finish, images and instances get loaded. This operation is executed in the UI thread (no background thread) and therefore blocks the UI. We should switch this to a background thread. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

2
10
0 / 0

[JBoss JIRA] Created: (JBIDE-8093) User gets no feedback about what's missing on "Create RSE Connection and Server" when launching an instance

by Andre Dietisheim (JIRA)

User gets no feedback about what's missing on "Create RSE Connection and Server" when launching an instance ----------------------------------------------------------------------------------------------------------- Key: JBIDE-8093 URL: https://issues.jboss.org/browse/JBIDE-8093 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: deltacloud Affects Versions: 3.2.0.CR1 Reporter: Andre Dietisheim Fix For: 3.2.x Attachments: rse-and-server-page1.png, rse-and-server-page2.png To launching an new instance, you have a wizard with 2 pages. 1) "Launch instance" page 2) "Create RSE Connection and Server" page The 2nd page does not inform (neither by decorations nor by errors in the title area) about what's missing. "Finish" is disabled and you only find out by looking closly at the fields which info is still missing and has to filled in. Ex. I choose "Determine server details from this remote file" (radio button). The path is already filled in but the "Local runtime" combo is empty. "Finish" is therefore disabled. I only find out about this by closlely looking at the form an detecting that the runtime is not chosen yet. The runtime combo is not decorated with an error marker. I also dont have an error in the title area. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
14
0 / 0

[JBoss JIRA] Created: (JBIDE-7772) cannot manage keys separately, need to open "launch instance" wizard for it

by Andre Dietisheim (JIRA)

cannot manage keys separately, need to open "launch instance" wizard for it --------------------------------------------------------------------------- Key: JBIDE-7772 URL: https://jira.jboss.org/browse/JBIDE-7772 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: deltacloud Affects Versions: 3.2.0.Beta2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.CR1 currently there's not item in the context menus, view menus, toolbars that allow me to manage keys. The only place where this might be reached is the "launch instance" wizard ("Manage" button) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

2
14
0 / 0

[JBoss JIRA] Created: (JBIDE-7523) Properties View: is not refreshed when correcting a connection url

by Andre Dietisheim (JIRA)

Properties View: is not refreshed when correcting a connection url ------------------------------------------------------------------ Key: JBIDE-7523 URL: https://jira.jboss.org/browse/JBIDE-7523 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.Beta2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.Beta2 -- 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

13 years, 1 month

2
12
0 / 0

[JBoss JIRA] Created: (JBIDE-8595) Guvnor is added to the context menu of *every* resource even though I havent enabled Guvnor

by Max Rydahl Andersen (JIRA)

Guvnor is added to the context menu of *every* resource even though I havent enabled Guvnor ------------------------------------------------------------------------------------------- Key: JBIDE-8595 URL: https://issues.jboss.org/browse/JBIDE-8595 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools Affects Versions: 3.2.0.Final Reporter: Max Rydahl Andersen Assignee: Brian Fitzpatrick Priority: Critical Fix For: 3.2.1, 3.3.0.M1 Right click a resource on any project and it will have Guvnor in the top root context menu. Same problem there was with Modeshape and Drools originally - not sure why Guvnor suddenly pops up here ;( -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-8722) CDI core test failures

by Alexey Kazakov (JIRA)

CDI core test failures ---------------------- Key: JBIDE-8722 URL: https://issues.jboss.org/browse/JBIDE-8722 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.3.0.M1 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M1 CDICoreAllTests CDI Core Tests org.jboss.tools.cdi.core.test.WeldJarTest testWeldJar(org.jboss.tools.cdi.core.test.WeldJarTest) junit.framework.AssertionFailedError: null at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertFalse(Assert.java:34) at junit.framework.Assert.assertFalse(Assert.java:41) at org.jboss.tools.cdi.core.test.WeldJarTest.testWeldJar(WeldJarTest.java:41) org.jboss.tools.cdi.core.test.DependentProjectTest testDependentProject(org.jboss.tools.cdi.core.test.DependentProjectTest) junit.framework.AssertionFailedError: null at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertNotNull(Assert.java:214) at junit.framework.Assert.assertNotNull(Assert.java:207) at org.jboss.tools.cdi.core.test.DependentProjectTest.assertBeanIsPresent(DependentProjectTest.java:77) at org.jboss.tools.cdi.core.test.DependentProjectTest.testDependentProject(DependentProjectTest.java:62) testCleanDependentProject(org.jboss.tools.cdi.core.test.DependentProjectTest) junit.framework.AssertionFailedError: null at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertNotNull(Assert.java:214) at junit.framework.Assert.assertNotNull(Assert.java:207) at org.jboss.tools.cdi.core.test.DependentProjectTest.assertBeanIsPresent(DependentProjectTest.java:77) at org.jboss.tools.cdi.core.test.DependentProjectTest.testCleanDependentProject(DependentProjectTest.java:90) testIndirectDependency(org.jboss.tools.cdi.core.test.DependentProjectTest) junit.framework.AssertionFailedError: null at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertFalse(Assert.java:34) at junit.framework.Assert.assertFalse(Assert.java:41) at org.jboss.tools.cdi.core.test.DependentProjectTest.testIndirectDependency(DependentProjectTest.java:144) testProjectDependencyLoading(org.jboss.tools.cdi.core.test.DependentProjectTest) junit.framework.AssertionFailedError: expected:<1> but was:<0> at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.failNotEquals(Assert.java:283) at junit.framework.Assert.assertEquals(Assert.java:64) at junit.framework.Assert.assertEquals(Assert.java:195) at junit.framework.Assert.assertEquals(Assert.java:201) at org.jboss.tools.cdi.core.test.DependentProjectTest.testProjectDependencyLoading(DependentProjectTest.java:156) org.jboss.tools.cdi.core.test.tck.validation.DependentProjectValidationTest testDependentProjects(org.jboss.tools.cdi.core.test.tck.validation.DependentProjectValidationTest) junit.framework.AssertionFailedError: Marker matches the 'Injection point declares a primitive type boolean that cannot be proxied by the container resolves to a bean TestBean3.foo with a normal scope \[JSR-299 §5.4.1\]' pattern wasn't found. Here is a list of found markers in /CDITest3/src/cdi/test3/TestBean3.java : [] at junit.framework.Assert.fail(Assert.java:47) at org.jboss.tools.tests.AbstractResourceMarkerTest.assertMarkerIsCreated(AbstractResourceMarkerTest.java:167) at org.jboss.tools.cdi.core.test.tck.validation.ValidationTest.assertMarkerIsCreated(ValidationTest.java:48) at org.jboss.tools.cdi.core.test.tck.validation.ValidationTest.assertMarkerIsCreated(ValidationTest.java:44) at org.jboss.tools.cdi.core.test.tck.validation.DependentProjectValidationTest.testDependentProjects(DependentProjectValidationTest.java:86) Probably the reason of these failures is this Exception: !ENTRY org.eclipse.core.resources 4 2 2011-04-12 17:09:24.167 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources". !STACK 0 java.lang.ArrayIndexOutOfBoundsException: 3 at org.eclipse.jdt.internal.compiler.classfmt.MethodInfoWithParameterAnnotations.getParameterAnnotations(MethodInfoWithParameterAnnotations.java:24) at org.eclipse.jdt.internal.core.ClassFileInfo.generateMethodInfos(ClassFileInfo.java:312) at org.eclipse.jdt.internal.core.ClassFileInfo.readBinaryChildren(ClassFileInfo.java:387) at org.eclipse.jdt.internal.core.ClassFile.buildStructure(ClassFile.java:97) at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:258) at org.eclipse.jdt.internal.core.SourceRefElement.generateInfos(SourceRefElement.java:107) at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:518) at org.eclipse.jdt.internal.core.BinaryType.getElementInfo(BinaryType.java:286) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:241) at org.eclipse.jdt.internal.core.BinaryType.isAnnotation(BinaryType.java:736) at org.jboss.tools.cdi.internal.core.scanner.FileSet.add(FileSet.java:39) at org.jboss.tools.cdi.core.CDICoreBuilder.buildJars(CDICoreBuilder.java:267) at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:174) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:717) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8306) Project Explorer has child node looking exactly the same as parent

by Denis Golovin (JIRA)

Project Explorer has child node looking exactly the same as parent ------------------------------------------------------------------ Key: JBIDE-8306 URL: https://issues.jboss.org/browse/JBIDE-8306 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.2.0.CR1 Reporter: Denis Golovin Assignee: Alexey Kazakov Fix For: 3.3.0.M1 Attachments: screenshot68.png Project with Enabled JSF/Struts capabilities contains child node that looks exactly the same as parent in Project Explorer view !screenshot68.png! It contains information about configuration (web deployment descriptor, JSF/Struts configuration, taglibs, beans and etc) and resources from web root. We have several way to give it a better look and usability: 1. (simple) find a right name/icon for it to describe content in it and remove redundant nodes from it (WebContent and web deployment descriptor, for instance, are already present under project in Projects Explorer) 2. Split it in several nodes to be shown as Project node siblings. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

5
13
0 / 0

[JBoss JIRA] Created: (JBIDE-8661) ModeShape Tools' SLF4J LoggerFactoryBinder Implementation Not Found On Classpath

by Dan Florian (JIRA)

ModeShape Tools' SLF4J LoggerFactoryBinder Implementation Not Found On Classpath -------------------------------------------------------------------------------- Key: JBIDE-8661 URL: https://issues.jboss.org/browse/JBIDE-8661 Project: Tools (JBoss Tools) Issue Type: Bug Components: modeshape Affects Versions: 3.2.0.Final Reporter: Dan Florian Assignee: Dan Florian Fix For: 3.2.1 With ModeShape 2.5.0.Beta1, the ModeShape jar no longer contains an implementation of LoggerFactoryBinder. This change in the MS jar revealed the MS Tools LoggerFactoryBinder implementation (which directs logging to the Eclipse logger) was not being found. This is because the MS Tools implementation was not in the correct package. SLF4J requires instances of LoggerFactoryBinder be in the "org.slf4j.impl" package. Need to repackage the MS Tools' impl. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8827) Cheatsheet's broken and incomplete for Seam 2.2 booking example

by Max Rydahl Andersen (JIRA)

Cheatsheet's broken and incomplete for Seam 2.2 booking example --------------------------------------------------------------- Key: JBIDE-8827 URL: https://issues.jboss.org/browse/JBIDE-8827 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 3.2.0.Final Reporter: Max Rydahl Andersen Assignee: Snjezana Peco Fix For: 3.2.1.M1, 3.3.0.M1 Chose "Seam 2.2 Booking Example - Ear (including a tutorial)" shows a great cheat sheet but the actions in there fails with IllegalArgumentExceptions and there seem to be missing links for large sections of the tutorial ? java.lang.IllegalArgumentException at org.eclipse.ui.part.FileEditorInput.getPath(FileEditorInput.java:208) at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:662) at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:638) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2860) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2768) at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2760) at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2711) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2707) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2691) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2682) at org.eclipse.ui.ide.IDE.openEditor(IDE.java:651) at org.eclipse.ui.ide.IDE.openEditor(IDE.java:610) at org.jboss.tools.project.examples.cheatsheet.actions.Ope -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-8818) org.jboss.tools.seam.core.test.refactoring.SeamRefactoringAllTests.testSeamComponentRename failed: Can't load component best

by Nick Boldt (JIRA)

org.jboss.tools.seam.core.test.refactoring.SeamRefactoringAllTests.testSeamComponentRename failed: Can't load component best ---------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-8818 URL: https://issues.jboss.org/browse/JBIDE-8818 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.1.M1 Reporter: Nick Boldt Assignee: Alexey Kazakov Fix For: 3.2.1.M1 https://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-3.2_stab... Regression org.jboss.tools.seam.core.test.refactoring.SeamRefactoringAllTests.testSeamComponentRename Failing for the past 1 build (Since Failed#169 ) Took 4 sec. add description Error Message Can't load component best Stacktrace junit.framework.AssertionFailedError: Can't load component best at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertNotNull(Assert.java:214) at org.jboss.tools.seam.core.test.refactoring.SeamComponentRefactoringTest.renameComponent(SeamComponentRefactoringTest.java:133) at org.jboss.tools.seam.core.test.refactoring.SeamComponentRefactoringTest.testSeamComponentRename(SeamComponentRefactoringTest.java:81) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2011