July 2012 - jbosstools-issues - Jboss List Archives

[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

11 years, 5 months

3
4
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

11 years, 5 months

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

11 years, 5 months

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

11 years, 5 months

3
6
0 / 0

[JBoss JIRA] (JBIDE-11927) Simple adding/removing Project Archives capabilities into project

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-11927: ----------------------------------------- Summary: Simple adding/removing Project Archives capabilities into project Key: JBIDE-11927 URL: https://issues.jboss.org/browse/JBIDE-11927 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Archives Affects Versions: 3.3.0.Beta3 Reporter: Jaroslav Jankovič Assignee: Rob Stryker Fix For: 3.3.0.CR1 It would be useful if we have "Configure -> Add/Remove Project Archive support" option. This option would add/remove Project Archive explorer into project in Project Explorer. Now, Project Archive explorer is visible only after creation of archive with Project Archives view. To remove Project Archives explorer now, .packages files has to be deleted. This approach is not much user friendly. -- 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

11 years, 5 months

4
12
0 / 0

[JBoss JIRA] (JBIDE-12088) merge all Teiid requirement builders (7.4 - 8.0) into a single target?

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-12088: ---------------------------------- Summary: merge all Teiid requirement builders (7.4 - 8.0) into a single target? Key: JBIDE-12088 URL: https://issues.jboss.org/browse/JBIDE-12088 Project: Tools (JBoss Tools) Issue Type: Bug Components: teiid Affects Versions: 3.3.0.CR1, 3.4.0.M1 Reporter: Nick Boldt Assignee: Barry LaFond Currently, there are 5 requirements builders for Teiid, from 7.4 - 8.0.Alpha1. You could, like with SOAP, merge these into a single builder so that it's easier to run tests against all supported runtimes via a single target. Thus your tests' requirements.properties file would read: {code}requirements=teiid{code} instead of {code}requirements=teiid-7.4.0.Final,teiid-7.5.0.Final,teiid-7.6.0.Final,teiid-8.0.0.Alpha1<code{ Would this be useful? If so, see attached patch. -- 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

11 years, 5 months

4
12
0 / 0

[JBoss JIRA] (JBIDE-11997) Move the hibernate templates and library providers out of org.jboss.tools.maven.core into org.jboss.tools.maven.hibernate

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-11997: ----------------------------------- Summary: Move the hibernate templates and library providers out of org.jboss.tools.maven.core into org.jboss.tools.maven.hibernate Key: JBIDE-11997 URL: https://issues.jboss.org/browse/JBIDE-11997 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: maven Affects Versions: 3.3.0.CR1 Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 3.3.1 Fixing JBIDE-11624 required adding a dependency on Dali to org.jboss.tools.maven.core. Long term, proper fix requires we move all maven-based hibernate library providers to org.jboss.tools.maven.hibernate and remove the Dali dependency from org.jboss.tools.maven.core. -- 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

11 years, 5 months

3
4
0 / 0

[JBoss JIRA] (JBIDE-12314) Extract file identification API for the Maven Source Lookup Plugin

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-12314: ----------------------------------- Summary: Extract file identification API for the Maven Source Lookup Plugin Key: JBIDE-12314 URL: https://issues.jboss.org/browse/JBIDE-12314 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: maven Affects Versions: 3.3.0.Final Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 3.4.0.M1 In order to implement JBIDE-8973, we should be able to reuse the file identification algorithms from the Source Lookup plugin. This means the identification part from Source Lookup needs to be extracted into an API. Possibly into a separate feature? moved back to the Maven core plugin? -- 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

11 years, 5 months

3
8
0 / 0

[JBoss JIRA] (JBIDE-12307) unified.target appears broken

by Paul Richardson (JIRA)

Paul Richardson created JBIDE-12307: --------------------------------------- Summary: unified.target appears broken Key: JBIDE-12307 URL: https://issues.jboss.org/browse/JBIDE-12307 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: target-platform Affects Versions: 3.4.x Environment: Either installed Eclipse Indigo or Juno Reporter: Paul Richardson Assignee: Nick Boldt Use of the unified.target fails as PDE target platform for both Indigo and Juno. *Indigo IDE* Use of the trunk version of unified.target results in org.lucene.core 3.5-4 not being found, which is true since only version 2.91 is available in the update site - http://download.jboss.org/jbosstools/updates/target-platform_3.4.juno.SR0... *Juno IDE* Use of the trunk version of unified.target results in package org.xmlpull.mxp1 not being found as a requirement of XStream. Both errors imply an incomplete target platform but does the fact that they are different errors imply that plugins in the installed IDE are assumed to be there? Should it not be possible to take an eclipse Indigo and develop against a Juno target platform? -- 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

11 years, 5 months

4
15
0 / 0

[JBoss JIRA] (JBIDE-11365) Allow the user to add "Restart Module" function as a keyboard-shortcut

by Adrian Mitev (JIRA)

Adrian Mitev created JBIDE-11365: ------------------------------------ Summary: Allow the user to add "Restart Module" function as a keyboard-shortcut Key: JBIDE-11365 URL: https://issues.jboss.org/browse/JBIDE-11365 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 3.3.0.Beta1 Reporter: Adrian Mitev Fix For: 3.3.0.Beta3 Because ANYTHING is possible and the infinite is unknown at zombo.com! -- 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

11 years, 5 months

4
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2012