July 2011 - jbosstools-issues - Jboss List Archives

[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-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: (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

[JBoss JIRA] Created: (JBIDE-9413) NLS missing messages

by George Gastaldi (JIRA)

NLS missing messages -------------------- Key: JBIDE-9413 URL: https://issues.jboss.org/browse/JBIDE-9413 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: George Gastaldi Priority: Trivial The following NLS messages are missing: {code:java} NLS missing message: J2EEModuleExportOperation_DestinationFileIsDirectoryError in: org.jboss.ide.eclipse.as.ui.Messages NLS missing message: J2EEModuleExportOperation_ErrorExportingArchive in: org.jboss.ide.eclipse.as.ui.Messages {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9305) CDI Validation problem markers should be removed when CDI support is disabled

by Alexey Kazakov (JIRA)

CDI Validation problem markers should be removed when CDI support is disabled ----------------------------------------------------------------------------- Key: JBIDE-9305 URL: https://issues.jboss.org/browse/JBIDE-9305 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 (with CDI support enabled) EXECUTE: Add any CDI problem. For instance: {code} public class Test { @Inject String foo; @Produces public String foo1() { return ""; } @Produces public String foo2() { return ""; } } {code} ASSERT: There is a CDI problem marker on @Inject String foo; EXECUTE: Disable CDI support in Project Properties page. Clean/re-build the project. ASSERT: The CDI problem disappeared. -- 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-9240) Add Class wizard in beans.xml editor throws exeption when attempting to add duplicate entries, but should properly validate input.

by Viacheslav Kabanovich (JIRA)

Add Class wizard in beans.xml editor throws exeption when attempting to add duplicate entries, but should properly validate input. ---------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-9240 URL: https://issues.jboss.org/browse/JBIDE-9240 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 EXECUTE: Open beans.xml editor and select 'Interceptors' node in 'Tree' tab. EXECUTE: Call from context menu 'Add Class' wizard, input 'MyClass' and finish. ASSERT: Node 'MyClass' appears. EXECUTE: Repeat second step with the same 'MyClass' input. ASSERT: Wizard disables finish and displays error message ''Interceptors' already contains class MyClass.'. FAILURE: Wizard allows to push 'Finish', writes error message with stack trace into the log and remains open. The same steps work for nodes 'Decorators' and 'Alternatives'. -- 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-9191) no provider name for org.jboss.tools.ws.jaxrs.feature

by Nick Boldt (JIRA)

no provider name for org.jboss.tools.ws.jaxrs.feature ----------------------------------------------------- Key: JBIDE-9191 URL: https://issues.jboss.org/browse/JBIDE-9191 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.3.0.M2 Reporter: Nick Boldt Assignee: Brian Fitzpatrick Fix For: 3.3.0.M3 Attachments: Screenshot-Forge-and-WS-JAXRS-missing-provider-names.png Missing provider name. check your feature.xml and add one (see other feature.xml and feature.properties files to learn how. Provider should be "JBoss by Red Hat". See also screenshot below: !Screenshot-Forge-and-WS-JAXRS-missing-provider-names! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9205) cdi.seam feature name is "Seam 3 Tools" but description says "Context and Dependency Injection Tools"

by Nick Boldt (JIRA)

cdi.seam feature name is "Seam 3 Tools" but description says "Context and Dependency Injection Tools" ----------------------------------------------------------------------------------------------------- Key: JBIDE-9205 URL: https://issues.jboss.org/browse/JBIDE-9205 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299), Seam Affects Versions: 3.3.0.M2 Reporter: Nick Boldt Assignee: Alexey Kazakov Priority: Minor Fix For: 3.3.0.M3 Attachments: Screenshot-cdi.seam-description-needs-tweaking.png cdi.seam feature name is "Seam 3 Tools" but description says "Context and Dependency Injection Tools". Should these align better, like we have for maven.feature or maven.seam.feature? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

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 July 2011