June 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-11988) Eclipse closes right after start

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBIDE-11988: ---------------------------------------- Summary: Eclipse closes right after start Key: JBIDE-11988 URL: https://issues.jboss.org/browse/JBIDE-11988 Project: Tools (JBoss Tools) Issue Type: Bug Components: teiid Affects Versions: 3.3.0.Beta2-SOA Environment: Ubuntu 12.04 64b and 11.10 64b OpenJDK 6 and 7 Reporter: Rastislav Wagner Assignee: Barry LaFond Priority: Blocker Fix For: 3.3.0.Beta3-SOA -- 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, 9 months

4
14
0 / 0

[JBoss JIRA] (JBDS-2174) installer says "Visual page editor is not supported for selected installation type" when switching to 32-bit

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBDS-2174: ----------------------------------------- Summary: installer says "Visual page editor is not supported for selected installation type" when switching to 32-bit Key: JBDS-2174 URL: https://issues.jboss.org/browse/JBDS-2174 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: installer Environment: OSX, default java run (so 64bit) Reporter: Max Rydahl Andersen Priority: Critical Fix For: 5.0.0.CR1 64-bit is selected on "Select Java VM" but when I select 32-bit it still says "Visual Page Editor is not supported for selected installation type". Shouldn't this be ok with 32-bit ? Maybe instead of using a label different per selection just put it after the 64-bit choice as: [ ] 32-bit (Visual Page editor is supported) [ ] 64-bit (Visual Page editor is not supported) -- 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, 9 months

3
3
0 / 0

[JBoss JIRA] (JBIDE-11894) Universal Installer odd - "bits"

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-11894: ----------------------------------- Summary: Universal Installer odd - "bits" Key: JBIDE-11894 URL: https://issues.jboss.org/browse/JBIDE-11894 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Burr Sutter -- 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, 9 months

4
12
0 / 0

[JBoss JIRA] (JBIDE-11509) Starting the AS/EAP when it already has multiple projects deployed

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-11509: ----------------------------------- Summary: Starting the AS/EAP when it already has multiple projects deployed Key: JBIDE-11509 URL: https://issues.jboss.org/browse/JBIDE-11509 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Burr Sutter When the server is started via "Run As on Server", and there were previous projects deployed (both inside/outside of the IDE), they tend to all fail to start. -- 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, 9 months

6
32
0 / 0

[JBoss JIRA] (JBDS-2184) Installer: Selecting 32-bit JVM, still displays Visual Page Editor not supported

by Burr Sutter (JIRA)

Burr Sutter created JBDS-2184: --------------------------------- Summary: Installer: Selecting 32-bit JVM, still displays Visual Page Editor not supported Key: JBDS-2184 URL: https://issues.jboss.org/browse/JBDS-2184 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: installer Environment: win 7 Reporter: Burr Sutter Attachments: Installer_JVM_selection_bug.png I have both Java 6 and Java 7, each with 32-bit and 64-bit versions. The installer defaulted to the 64-bit JRE (I suspect that is first in the PATH), which is fine but I changed it to the 32-bit JDK. Upon switching to the 32-bit Java 7 JDK - the message "Visual Page Editor is not supported for this Installation Type" remains on screen. -- 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, 9 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-8413) Savara->Generate->WSDL action does nothing when invoked on Choreography Description file (.cdm)

by Denis Golovin (JIRA)

Savara->Generate->WSDL action does nothing when invoked on Choreography Description file (.cdm) ----------------------------------------------------------------------------------------------- Key: JBIDE-8413 URL: https://issues.jboss.org/browse/JBIDE-8413 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Denis Golovin Only warnings reported in console: {noformat} Feb 11, 2011 1:45:12 PM org.pi4soa.common.util.PropertyUtil loadXML INFO: Located pi4soa XML configuration Feb 11, 2011 1:45:12 PM org.pi4soa.cdl.interfaces.InterfaceFactory <clinit> WARNING: Failed to find interface introspector: org.pi4soa.wsdl.interfaces.WSDLInterfaceIntrospector {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

8
12
0 / 0

[JBoss JIRA] Created: (JBIDE-8415) Savara Preferences Page layout impovements

by Denis Golovin (JIRA)

Savara Preferences Page layout impovements ------------------------------------------- Key: JBIDE-8415 URL: https://issues.jboss.org/browse/JBIDE-8415 Project: Tools (JBoss Tools) Issue Type: Bug Components: Savara Affects Versions: 3.2.0.CR1 Reporter: Denis Golovin Attachments: screenshot15.png !screenshot15.png! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

8
12
0 / 0

[JBoss JIRA] (JBIDE-10363) Materialize Library : Remove the gradle nature when materializing com.springsource.sts.gradle.classpathcontainer

by Fred Bricon (Created) (JIRA)

Materialize Library : Remove the gradle nature when materializing com.springsource.sts.gradle.classpathcontainer ---------------------------------------------------------------------------------------------------------------- Key: JBIDE-10363 URL: https://issues.jboss.org/browse/JBIDE-10363 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: common/jst/core Affects Versions: 3.3.0.M5 Environment: STS 2.8.1 Reporter: Fred Bricon Assignee: Alexey Kazakov Priority: Minor Fix For: 3.3.0.Beta1 Materializing the Gradle Library works fine, but we'd need to also remove the gradle nature and display a warning when doing so (similar to what we do with [Maven|JBIDE-9878]). -- 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, 9 months

4
5
0 / 0

[JBoss JIRA] (JBIDE-11653) Errors running builder 'JAX-RS Builder' on project 'ticket-monster'.

by Marius Bogoevici (JIRA)

Marius Bogoevici created JBIDE-11653: ---------------------------------------- Summary: Errors running builder 'JAX-RS Builder' on project 'ticket-monster'. Key: JBIDE-11653 URL: https://issues.jboss.org/browse/JBIDE-11653 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: Marius Bogoevici java.lang.ClassCastException: org.eclipse.jdt.internal.core.TypeParameter cannot be cast to org.eclipse.jdt.core.IType at org.jboss.tools.ws.jaxrs.core.jdt.JavaMethodSignaturesVisitor.visit(JavaMethodSignaturesVisitor.java:88) at org.eclipse.jdt.core.dom.MethodDeclaration.accept0(MethodDeclaration.java:489) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514) at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2585) at org.eclipse.jdt.core.dom.TypeDeclaration.accept0(TypeDeclaration.java:484) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514) at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2585) at org.eclipse.jdt.core.dom.CompilationUnit.accept0(CompilationUnit.java:219) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514) at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveMethodSignature(JdtUtils.java:587) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.internalCreateResourceMethod(JaxrsElementFactory.java:236) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.createResource(JaxrsElementFactory.java:148) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessor.preprocessResourceChangesOnScopeAdditionOrChange(ResourceChangedProcessor.java:531) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessor.processResourceChangesOnScopeAdditionOrChange(ResourceChangedProcessor.java:502) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessor.processEvent(ResourceChangedProcessor.java:177) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessor.processEntireProject(ResourceChangedProcessor.java:108) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessor.processAffectedResources(ResourceChangedProcessor.java:81) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelBuilder.build(JaxrsMetamodelBuilder.java:122) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelBuilder.build(JaxrsMetamodelBuilder.java:82) 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, 9 months

5
11
0 / 0

[JBoss JIRA] (JBIDE-11943) CLONE - CLONE - WS Component N&N

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-11943: ------------------------------------------- Summary: CLONE - CLONE - WS Component N&N Key: JBIDE-11943 URL: https://issues.jboss.org/browse/JBIDE-11943 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Webservices Reporter: Denis Golovin Assignee: Brian Fitzpatrick Fix For: 3.3.0.Beta3 https://jira.jboss.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=pro... -- 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, 9 months

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