August 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-9506) This catch block hides stack trace and as result real problem under it

by Fisheye JIRA Integration (JIRA)

This catch block hides stack trace and as result real problem under it ---------------------------------------------------------------------- Key: JBIDE-9506 URL: https://issues.jboss.org/browse/JBIDE-9506 Project: Tools (JBoss Tools) Issue Type: Sub-task Affects Versions: 3.2.1.M1, 3.3.0.M1 Reporter: Fisheye JIRA Integration Fix For: 3.3.0.Final Created by Andre Dietisheim from Denis Golovin's Crucible comment on JBoss7ManagerServicePoller.java line 158 https://source.jboss.org/cru/REV-JBIDE-4#c25 : This catch block hides stack trace and as result real problem under it -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBDS-1713) m2e features disappear after installing egit

by Libor Zoubek (JIRA)

m2e features disappear after installing egit -------------------------------------------- Key: JBDS-1713 URL: https://issues.jboss.org/browse/JBDS-1713 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: 3rdPartyCertification, updatesite Affects Versions: 5.0.0.M2 Environment: Linux x86 Reporter: Libor Zoubek Priority: Blocker Fix For: 5.0.0.M3 I am facing very weird behaviour of JBDS. If I install m2e (only) from extras site, it takes longer as usuall. But only the phase saying 'Commiting the provisioning information' and JBDS startup time is affected (before JBDS asks for workspace). Installation of every other extra feature is slower than usual. The worst thing is, that after I install egit (maybe it is not related to egit, but just other extra feature) I cannot use m2e features in JBDS, it just disappears. But at the same time plugins can bee seen in installation history. I tried to install just egit or just findBugs and after installing these there is no time penalty at startup or when installing othre extras and these features are available as expected. Thatswhy I think, there is something bad in our m2e feature. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
8
0 / 0

[JBoss JIRA] Created: (JBDS-1792) Installation of m2e fails and completely breaks JBDS 5

by Nick Boldt (JIRA)

Installation of m2e fails and completely breaks JBDS 5 ------------------------------------------------------ Key: JBDS-1792 URL: https://issues.jboss.org/browse/JBDS-1792 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: 3rdPartyCertification, updatesite Affects Versions: 4.1.0.CR3, 5.0.0.M2 Reporter: Libor Zoubek Assignee: Nick Boldt Priority: Blocker Fix For: 4.1.0.CR3, 5.0.0.M3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
7
0 / 0

[JBoss JIRA] Created: (JBIDE-9509) Tests: JSTDeployBinaryChildModuleTest.testStandardBinaryChildDeployment fails witch tycho (and on hudson)

by Andre Dietisheim (JIRA)

Tests: JSTDeployBinaryChildModuleTest.testStandardBinaryChildDeployment fails witch tycho (and on hudson) --------------------------------------------------------------------------------------------------------- Key: JBIDE-9509 URL: https://issues.jboss.org/browse/JBIDE-9509 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Andre Dietisheim JSTDeployBinaryChildModuleTest.testStandardBinaryChildDeployment fails in tycho (and on hudson) but passes in Eclipse PDE. Error report on hudson: https://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/jbosstools-3.... The test fails when asserting the presence of the root folder at line 56: {code} assertTrue(rootFolder.toFile().exists()); {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-9345) AS7: remove unneeded additional indirection in service usage

by Andre Dietisheim (JIRA)

AS7: remove unneeded additional indirection in service usage ------------------------------------------------------------ Key: JBIDE-9345 URL: https://issues.jboss.org/browse/JBIDE-9345 Project: Tools (JBoss Tools) Issue Type: Enhancement Affects Versions: 3.3.0.M3 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.x AS tooling uses an osgi service to interact with the as7 server. This service is implemented in AS7Manager. This manager is not directly exposed but there's an additional indirection to it: JBoss7ManagerService. This was initially done because we thought about offerding additional functionalities which did not work out. We should now remove this additional indirection/wrapping since there's no sense to it, it only makes code harder to read. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-1692) Documentation plugins with context sensitive help

by Max Andersen (JIRA)

Documentation plugins with context sensitive help ------------------------------------------------- Key: JBIDE-1692 URL: http://jira.jboss.com/jira/browse/JBIDE-1692 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 2.0.0.GA Reporter: Max Andersen Priority: Critical Fix For: 2.1 Get doc into eclipse format Have reference docs with context sensitive links -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

6
19
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-239) Wrong link to Visual Web Tools Reference Guide in Seam Developer Tools Reference Guide

by Martin Malina (JIRA)

Wrong link to Visual Web Tools Reference Guide in Seam Developer Tools Reference Guide -------------------------------------------------------------------------------------- Key: TOOLSDOC-239 URL: https://issues.jboss.org/browse/TOOLSDOC-239 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Security Level: Public (Everyone can see) Components: Seam Developer Tools Reference Guide Affects Versions: 3.2.1.Final Reporter: Martin Malina Assignee: Isaac Rooskov Fix For: 3.2.1.Final Not sure if this is even worth a JIRA, but anyway... http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Developer_Stud... 8.1. Visual Page Editor ... You can also read more about Visual Page Editor in Visual Page Editor chapter of "Visual Web Tools Reference Guide". This link points to http://download.jboss.org/jbosstools/nightly-docs/en/jsf/html/editors.htm... . I suppose it should point to the same product documentation, i.e. http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Developer_Stud... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-9457) test failures in org.jboss.tools.vpe.docbook.test

by Nick Boldt (JIRA)

test failures in org.jboss.tools.vpe.docbook.test ------------------------------------------------- Key: JBIDE-9457 URL: https://issues.jboss.org/browse/JBIDE-9457 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: testing, Visual Page Editor core Affects Versions: 3.3.0.M3 Reporter: Nick Boldt Assignee: Max Rydahl Andersen Fix For: 3.3.0.M4 svn co http://svn.jboss.org/repos/jbosstools/trunk/ cd trunk; mvn clean install [INFO] org.jboss.tools.vpe.docbook.test .................. FAILURE [44.280s] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-9306) Incremental validation doesn't re-validate related alternatives.

by Alexey Kazakov (JIRA)

Incremental validation doesn't re-validate related alternatives. ---------------------------------------------------------------- Key: JBIDE-9306 URL: https://issues.jboss.org/browse/JBIDE-9306 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.3.0.M2 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.3.0.M3 EXECUTE: Create a CDI project (w/ CDI support enabled) EXECUTE: Add the following classes to the project source folder: {code} package org.jboss; import javax.enterprise.inject.Alternative; @Alternative public class Test { } {code} {code} package org.jboss; import javax.enterprise.inject.Alternative; @Alternative public class Test1 extends Test { } {code} {code} package org.jboss; import javax.inject.Inject; public class Test3 { @Inject Test test; } {code} And beans.xml (should be placed in <source folder>/META-INF/ or <web content>/WEB-INF/ in case of dynamic web project): {code} <?xml version="1.0" encoding="UTF-8"?> <beans xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://jboss.org/schema/cdi/beans_1_0.xsd"> <alternatives> <class>org.jboss.Test1</class> </alternatives> </beans> {code} EXECUTE: Build the project. ASSERT: There is no CDI problem markers on Test3.test field. EXECUTE: Replace the beans.xml be the following file: {code} <?xml version="1.0" encoding="UTF-8"?> <beans xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://jboss.org/schema/cdi/beans_1_0.xsd"> </beans> {code} EXECUTE: Save the file. {color:red}FAILURE:{color} The following CDI problem marker doesn't appear on Test3.test field: "No bean is eligible for injection to the injection point [JSR-299 §5.2.1]" {color:green}ASSERT:{color} The following CDI problem marker appears on Test3.test field: "No bean is eligible for injection to the injection point [JSR-299 §5.2.1]" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-9423) CDI Validation throws NPE

by Alexey Kazakov (JIRA)

CDI Validation throws NPE ------------------------- Key: JBIDE-9423 URL: https://issues.jboss.org/browse/JBIDE-9423 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdi Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.3.0.M3 This quick fix should offer to Delete @Specializes annotation Test case: EXECUTE: Create CDI project EXECUTE: Create TestBean class {code} package org.test; import javax.enterprise.inject.Specializes; import javax.interceptor.Interceptor; @Interceptor @FooBinding @Specializes public class TestBean extends AnyBean{ public String produce(){ return "a"; } } {code} ASSERT: @Specializes annotation should be marked by problem marker EXECUTE: Point mouse to @Specializes annotation ASSERT: Text hover with quick fixe appears EXECUTE: Create TestBean2 class {code} package org.test; import javax.decorator.Decorator; import javax.decorator.Delegate; import javax.enterprise.inject.Specializes; import javax.inject.Inject; @Decorator @Specializes public class TestBean2 extends AnyBean{ @Inject @Delegate @AAnnotation String str; public String produce(){ return str; } } {code} ASSERT: @Specializes annotation should be marked by problem marker EXECUTE: Point mouse to @Specializes annotation ASSERT: Text hover with quick fixe appears -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
6
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 August 2011