September 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-12485) Move JAX-RS validation into JBoss Tools validation, aside of CDI validation

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-12485: ------------------------------------- Summary: Move JAX-RS validation into JBoss Tools validation, aside of CDI validation Key: JBIDE-12485 URL: https://issues.jboss.org/browse/JBIDE-12485 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Webservices Affects Versions: 4.0.0.M1 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.0.0.M1 Use org.jboss.tools.common.validation to validate the JAX-RS metamodel and provide the user with settings to configure the problem level (Error/Warning/Ignore) for each kind of problem that the validation can detect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
5
0 / 0

[JBoss JIRA] (JBIDE-12488) Report a warning if no JAX-RS activator (or multiple ones) exist in the project

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-12488: ------------------------------------- Summary: Report a warning if no JAX-RS activator (or multiple ones) exist in the project Key: JBIDE-12488 URL: https://issues.jboss.org/browse/JBIDE-12488 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Webservices Affects Versions: 3.3.0.Final Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.0.0.M1 If no JAX-RS application (java style or web.xml style) has been defined, the JAX-RS endpoints will be unreachable (the JAX-RS implementation may not be started). On the other side, having multiple ones may lead to user errors (expecting different URIs). Report a warning for now, as not all kinds of activators are supported (vendor specific ones for instance) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
9
0 / 0

[JBoss JIRA] (JBIDE-12376) Maven Library Provider throws NPE if template contains some plugin

by Snjezana Peco (JIRA)

Snjezana Peco created JBIDE-12376: ------------------------------------- Summary: Maven Library Provider throws NPE if template contains some plugin Key: JBIDE-12376 URL: https://issues.jboss.org/browse/JBIDE-12376 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 3.3.1 Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 3.4.0.M1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
4
0 / 0

[JBoss JIRA] (JBIDE-12577) Unknown version of birt preset

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-12577: ----------------------------------------- Summary: Unknown version of birt preset Key: JBIDE-12577 URL: https://issues.jboss.org/browse/JBIDE-12577 Project: Tools (JBoss Tools) Issue Type: Bug Components: birt Affects Versions: 4.0.0.Alpha1 Reporter: Jaroslav Jankovič Assignee: Snjezana Peco Fix For: 4.0.0.Alpha1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

4
6
0 / 0

[JBoss JIRA] (JBIDE-10398) OpenShift Express : Can not delete OpenShift project

by Fred Bricon (Created) (JIRA)

OpenShift Express : Can not delete OpenShift project ---------------------------------------------------- Key: JBIDE-10398 URL: https://issues.jboss.org/browse/JBIDE-10398 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.M5 Environment: windows 7 Reporter: Fred Bricon Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 Whenever I try to physically delete my openshift project from the workspace, I get a popup with the following errors : {noformat} Problems encountered while deleting resources. Could not delete '/hello/.git'. Problems encountered while deleting resources. Problems encountered while deleting files. Could not delete: C:\Users\Fred Bricon\git\hello\.git\objects\pack\pack-10eb864ff7ab3a1edfc8b868c90a743fdee571db.pack. Could not delete: C:\Users\Fred Bricon\git\hello\.git\objects\pack. Could not delete: C:\Users\Fred Bricon\git\hello\.git\objects. Could not delete: C:\Users\Fred Bricon\git\hello\.git. Could not delete 'C:\Users\Fred Bricon\git\hello'. {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

6
19
0 / 0

[JBoss JIRA] (JBIDE-11652) Errors running builder 'JavaScript Validator' on project 'ticket-monster'.

by Marius Bogoevici (JIRA)

Marius Bogoevici created JBIDE-11652: ---------------------------------------- Summary: Errors running builder 'JavaScript Validator' on project 'ticket-monster'. Key: JBIDE-11652 URL: https://issues.jboss.org/browse/JBIDE-11652 Project: Tools (JBoss Tools) Issue Type: Sub-task Affects Versions: 3.3.0.Beta3 Reporter: Marius Bogoevici Stacktrace: java.lang.ArrayIndexOutOfBoundsException: 11 at org.eclipse.wst.jsdt.internal.compiler.ast.CaseStatement.resolveCase(CaseStatement.java:82) at org.eclipse.wst.jsdt.internal.compiler.ast.SwitchStatement.resolve(SwitchStatement.java:156) at org.eclipse.wst.jsdt.internal.compiler.ast.AbstractMethodDeclaration.resolveStatements(AbstractMethodDeclaration.java:350) at org.eclipse.wst.jsdt.internal.compiler.ast.MethodDeclaration.resolveStatements(MethodDeclaration.java:137) at org.eclipse.wst.jsdt.internal.compiler.ast.AbstractMethodDeclaration.resolve(AbstractMethodDeclaration.java:304) at org.eclipse.wst.jsdt.internal.compiler.ast.AbstractMethodDeclaration.resolve(AbstractMethodDeclaration.java:375) at org.eclipse.wst.jsdt.internal.compiler.ast.FunctionExpression.resolveType(FunctionExpression.java:58) at org.eclipse.wst.jsdt.internal.compiler.ast.ObjectLiteralField.resolveType(ObjectLiteralField.java:70) at org.eclipse.wst.jsdt.internal.compiler.ast.ObjectLiteral.resolveType(ObjectLiteral.java:80) at org.eclipse.wst.jsdt.internal.compiler.ast.MessageSend.resolveType(MessageSend.java:279) at org.eclipse.wst.jsdt.internal.compiler.ast.Expression.resolve(Expression.java:477) at org.eclipse.wst.jsdt.internal.compiler.ast.AbstractMethodDeclaration.resolveStatements(AbstractMethodDeclaration.java:350) at org.eclipse.wst.jsdt.internal.compiler.ast.MethodDeclaration.resolveStatements(MethodDeclaration.java:137) at org.eclipse.wst.jsdt.internal.compiler.ast.AbstractMethodDeclaration.resolve(AbstractMethodDeclaration.java:304) at org.eclipse.wst.jsdt.internal.compiler.ast.AbstractMethodDeclaration.resolve(AbstractMethodDeclaration.java:375) at org.eclipse.wst.jsdt.internal.compiler.ast.FunctionExpression.resolveType(FunctionExpression.java:58) at org.eclipse.wst.jsdt.internal.compiler.ast.ObjectLiteralField.resolveType(ObjectLiteralField.java:70) at org.eclipse.wst.jsdt.internal.compiler.ast.ObjectLiteral.resolveType(ObjectLiteral.java:80) at org.eclipse.wst.jsdt.internal.compiler.ast.MessageSend.resolveType(MessageSend.java:279) at org.eclipse.wst.jsdt.internal.compiler.ast.Expression.resolve(Expression.java:477) at org.eclipse.wst.jsdt.internal.compiler.ast.AbstractMethodDeclaration.resolveStatements(AbstractMethodDeclaration.java:350) at org.eclipse.wst.jsdt.internal.compiler.ast.MethodDeclaration.resolveStatements(MethodDeclaration.java:137) at org.eclipse.wst.jsdt.internal.compiler.ast.AbstractMethodDeclaration.resolve(AbstractMethodDeclaration.java:304) at org.eclipse.wst.jsdt.internal.compiler.ast.AbstractMethodDeclaration.resolve(AbstractMethodDeclaration.java:375) at org.eclipse.wst.jsdt.internal.compiler.ast.FunctionExpression.resolveType(FunctionExpression.java:58) at org.eclipse.wst.jsdt.internal.compiler.ast.MessageSend.resolveType(MessageSend.java:267) at org.eclipse.wst.jsdt.internal.compiler.ast.Expression.resolve(Expression.java:477) at org.eclipse.wst.jsdt.internal.compiler.ast.AbstractMethodDeclaration.resolveStatements(AbstractMethodDeclaration.java:350) at org.eclipse.wst.jsdt.internal.compiler.ast.MethodDeclaration.resolveStatements(MethodDeclaration.java:137) at org.eclipse.wst.jsdt.internal.compiler.ast.AbstractMethodDeclaration.resolve(AbstractMethodDeclaration.java:304) at org.eclipse.wst.jsdt.internal.compiler.ast.AbstractMethodDeclaration.resolve(AbstractMethodDeclaration.java:375) at org.eclipse.wst.jsdt.internal.compiler.ast.FunctionExpression.resolveType(FunctionExpression.java:58) at org.eclipse.wst.jsdt.internal.compiler.ast.MessageSend.resolveType(MessageSend.java:279) at org.eclipse.wst.jsdt.internal.compiler.ast.Expression.resolve(Expression.java:477) at org.eclipse.wst.jsdt.internal.compiler.ast.CompilationUnitDeclaration.resolve(CompilationUnitDeclaration.java:394) at org.eclipse.wst.jsdt.internal.compiler.Compiler.process(Compiler.java:604) at org.eclipse.wst.jsdt.internal.compiler.Compiler.compile(Compiler.java:356) at org.eclipse.wst.jsdt.internal.core.builder.AbstractImageBuilder.compile(AbstractImageBuilder.java:288) at org.eclipse.wst.jsdt.internal.core.builder.BatchImageBuilder.compile(BatchImageBuilder.java:86) at org.eclipse.wst.jsdt.internal.core.builder.AbstractImageBuilder.compile(AbstractImageBuilder.java:227) at org.eclipse.wst.jsdt.internal.core.builder.BatchImageBuilder.build(BatchImageBuilder.java:58) at org.eclipse.wst.jsdt.internal.core.builder.JavaBuilder.buildAll(JavaBuilder.java:291) at org.eclipse.wst.jsdt.internal.core.builder.JavaBuilder.build(JavaBuilder.java:194) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:394) at org.eclipse.core.internal.resources.Project$1.run(Project.java:618) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.core.internal.resources.Project.internalBuild(Project.java:597) at org.eclipse.core.internal.resources.Project.build(Project.java:114) at com.google.gdt.eclipse.core.BuilderUtilities$2.runInWorkspace(BuilderUtilities.java:202) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

6
49
0 / 0

[JBoss JIRA] (JBIDE-12291) wtp ServerToolTip too aggressive, opens empty tooltips, no way to extend as we need

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-12291: ----------------------------------- Summary: wtp ServerToolTip too aggressive, opens empty tooltips, no way to extend as we need Key: JBIDE-12291 URL: https://issues.jboss.org/browse/JBIDE-12291 Project: Tools (JBoss Tools) Issue Type: Bug Components: UpStream Affects Versions: 3.3.0.Final Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.3.2, 3.4.0.M1 Upstream's tooltips open even when there's nothing to show. There is a way to extend it, however, that way is only valid for adding information if a server or module is selected. IT in no way allows us to customize the tooltip for something like an XPath node or a fileset node or any other custom node we might have. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
6
0 / 0

[JBoss JIRA] (JBDS-2298) JBT shows subset of Mylyn repos configured for JBDS

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-2298: ---------------------------------- Summary: JBT shows subset of Mylyn repos configured for JBDS Key: JBDS-2298 URL: https://issues.jboss.org/browse/JBDS-2298 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: 3rdPartyCertification Affects Versions: 6.0.0.Alpha2 Environment: JBDS: Version: 5.0.0.GA Build id: v20120615-1714-H213-GA Build date: 20120615-1714 JBT: http://download.jboss.org/jbosstools/updates/JBossTools-4.0.0.Alpha2a.core/ Reporter: Len DiMaggio Fix For: 6.0.0.Beta1 See attached screenshots - why wouldn't we include the JBoss community and JIRA repos for JBT? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

5
11
0 / 0

[JBoss JIRA] (JBIDE-12491) JBT Doesn't place the JDBC Driver correctly

by Daniel Hinojosa (JIRA)

Daniel Hinojosa created JBIDE-12491: --------------------------------------- Summary: JBT Doesn't place the JDBC Driver correctly Key: JBIDE-12491 URL: https://issues.jboss.org/browse/JBIDE-12491 Project: Tools (JBoss Tools) Issue Type: Bug Environment: Juno, JBT Daily Plugin Reporter: Daniel Hinojosa in the ds.xml file. the following gets generated under driver. Works fine under regular seam-gen. {code:xml} <?xml version="1.0" encoding="UTF-8"?> <datasources xmlns="http://www.jboss.org/ironjacamar/schema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.org/ironjacamar/schema http://www.jboss.org/ironjacamar/schema/datasources_1_0.xsd"> <datasource jndi-name="nationalparkDatasource" enabled="true" use-java-context="true" pool-name="nationalparkDatasource_pool"> <connection-url>jdbc:hsqldb:MyDB</connection-url> <driver>[Ljava.lang.String;@4633819a</driver> <security> <user-name>sa</user-name> <password></password> </security> </datasource> </datasources> {code:xml} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

7
22
0 / 0

[JBoss JIRA] (JBIDE-12419) archives core should not have references to NLS class in src/main

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-12419: ----------------------------------- Summary: archives core should not have references to NLS class in src/main Key: JBIDE-12419 URL: https://issues.jboss.org/browse/JBIDE-12419 Project: Tools (JBoss Tools) Issue Type: Bug Components: Archives Affects Versions: 3.3.1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.3.2, 3.4.0.M1 The old use case to run project archives from cmd line requires a strict set of jars. References to NLS class are not allowed. Problem can be seen in build unit test SimpleAntTest Error Message The ant task did not successfully complete. BUILD FAILED /mnt/hudson_workspace/workspace/jbosstools-3.3_trunk.component--archives/sources/tests/org.jboss.ide.eclipse.archives.test/target/work/data/AntTest/build.xml:25: java.lang.NoClassDefFoundError: org/eclipse/osgi/util/NLS Stacktrace junit.framework.AssertionFailedError: The ant task did not successfully complete. BUILD FAILED /mnt/hudson_workspace/workspace/jbosstools-3.3_trunk.component--archives/sources/tests/org.jboss.ide.eclipse.archives.test/target/work/data/AntTest/build.xml:25: java.lang.NoClassDefFoundError: org/eclipse/osgi/util/NLS -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

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 2012