February 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-10835) "assertion failed" error clicking on JSP Error Marker

by Daniel Atallah (JIRA)

Daniel Atallah created JBIDE-10835: -------------------------------------- Summary: "assertion failed" error clicking on JSP Error Marker Key: JBIDE-10835 URL: https://issues.jboss.org/browse/JBIDE-10835 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.3.0.M5 Environment: Windows 7 64-bit, Eclipse 3.7.1 32-bit, Java 1.6.0_u30 Reporter: Daniel Atallah Assignee: Alexey Kazakov When clicking on a JSP Problem in the "Marker" view, the JSP file is opened, but instead of focusing the relevant line, an error dialog is displayed with the following text: An error has occurred. See error log for more details. assertion failed: Nothing additional is in the details. The error log contains the following stack trace: !ENTRY org.eclipse.jface 4 2 2012-02-08 16:47:09.198 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface". !STACK 0 org.eclipse.core.runtime.AssertionFailedException: assertion failed: at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110) at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96) at org.eclipse.ui.part.MultiPageEditorPart.setActivePage(MultiPageEditorPart.java:1065) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.gotoMarker(JSPMultiPageEditor.java:542) at org.eclipse.ui.ide.IDE.gotoMarker(IDE.java:408) at org.eclipse.ui.ide.IDE.openEditor(IDE.java:1117) at org.eclipse.ui.internal.views.markers.ExtendedMarkersView.openMarkerInEditor(ExtendedMarkersView.java:1719) at org.eclipse.ui.internal.views.markers.ExtendedMarkersView.openSelectedMarkers(ExtendedMarkersView.java:1188) at org.eclipse.ui.internal.views.markers.ExtendedMarkersView$5.open(ExtendedMarkersView.java:578) at org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:48) at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:866) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:864) at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1152) at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1256) at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:275) at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:269) at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:309) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) This happens for any JSP Problem that I click on from the Markers view. -- 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

12 years, 7 months

4
16
0 / 0

[JBoss JIRA] (JBIDE-10972) JSF tooling is not properly installed to Eclipse for Java Developers

by Vlado Pakan (JIRA)

Vlado Pakan created JBIDE-10972: ----------------------------------- Summary: JSF tooling is not properly installed to Eclipse for Java Developers Key: JBIDE-10972 URL: https://issues.jboss.org/browse/JBIDE-10972 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.3.0.Beta1 Environment: Eclipse Indigo SR1 for Java Developers Reporter: Vlado Pakan Assignee: Alexey Kazakov Fix For: 3.3.0.Beta1 Steps to reproduce: 1. install Eclipse Indigo SR1 for Java Developers 2. Install these features: JBoss Tools JSF, JBoss Tools Visual Page Editor, JBOssAS Tools 3. Create JSF 1.2 Kick Start project There is this error in Error Log: "Project facet wst.jsdt.web has not been defined. It is used in plugin org.eclipse.jst.server.core." To fix this error feature Eclipse Web Developer Tools (org.eclipse.wst.web_ui.feature.feature.group) has to be installed. This dependency has to be automatically resolved without manual installation required. -- 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

12 years, 7 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-10872) EL incremental validation doesn't work for complex ELs.

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-10872: -------------------------------------- Summary: EL incremental validation doesn't work for complex ELs. Key: JBIDE-10872 URL: https://issues.jboss.org/browse/JBIDE-10872 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.3.0.Beta1 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.3.0.Beta1 -- 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

12 years, 7 months

3
3
0 / 0

[JBoss JIRA] (JBIDE-10359) show in Forge console does not offer to start forge

by Max Rydahl Andersen (Created) (JIRA)

show in Forge console does not offer to start forge --------------------------------------------------- Key: JBIDE-10359 URL: https://issues.jboss.org/browse/JBIDE-10359 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: forge Affects Versions: 3.3.0.M5 Reporter: Max Rydahl Andersen Assignee: Koen Aers Priority: Blocker Fix For: 3.3.0.Beta1 -- 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

12 years, 7 months

3
3
0 / 0

[JBoss JIRA] (JBIDE-10342) RSE Server Shutdown Does Not Work with AS7 / AS7.1

by Martin Malina (Created) (JIRA)

RSE Server Shutdown Does Not Work with AS7 / AS7.1 -------------------------------------------------- Key: JBIDE-10342 URL: https://issues.jboss.org/browse/JBIDE-10342 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers Affects Versions: 3.3.0.M4 Reporter: Martin Malina Assignee: Rob Stryker Priority: Blocker Fix For: 3.3.0.Beta1 RSE Server stop over ssh does not work for AS 7.x. Server start works, but please make sure both are working. -- 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

12 years, 7 months

7
14
0 / 0

[JBoss JIRA] (JBIDE-10033) Forge View shows up in odd location

by Burr Sutter (Created) (JIRA)

Forge View shows up in odd location ----------------------------------- Key: JBIDE-10033 URL: https://issues.jboss.org/browse/JBIDE-10033 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Environment: JBoss Tools 3.3.M4, Eclipse 3.7 Java EE 32-bit, 32-bit Java 1.6 JDK Reporter: Burr Sutter Attachments: Forge_JBossTools.png Forge is accessible via Ctrl-4 or Window-Show View-Other When requested it shows up on the right-side of my Eclipse window - tall & skinny, this might be because I had previously launched one of the quickstarts that displayed the cheatsheet. See screenshot. -- 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

12 years, 7 months

9
12
0 / 0

[JBoss JIRA] (JBIDE-10272) Automatically Start Forge When Eclipse Starts

by Koen Aers (Created) (JIRA)

Automatically Start Forge When Eclipse Starts --------------------------------------------- Key: JBIDE-10272 URL: https://issues.jboss.org/browse/JBIDE-10272 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: forge Reporter: Koen Aers Assignee: Koen Aers Fix For: 3.3.0.Beta1 This feature needs to be controlled by a preference setting. -- 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

12 years, 7 months

3
2
0 / 0

[JBoss JIRA] (JBIDE-10840) Consumption of sun.misc.Signal makes Tycho 0.14 fails because of non-OSGi conformance

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-10840: -------------------------------------- Summary: Consumption of sun.misc.Signal makes Tycho 0.14 fails because of non-OSGi conformance Key: JBIDE-10840 URL: https://issues.jboss.org/browse/JBIDE-10840 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Environment: any Reporter: Mickael Istria Assignee: Koen Aers Priority: Blocker When building with Tycho, I get: [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.14.0-SNAPSHOT:compile (default-compile) on project org.jboss.tools.forge.runtime.ext: Compilation failure: Compilation failure: [ERROR] /home/mistria/workspaceJBossTools/trunk/forge/plugins/org.jboss.tools.forge.runtime.ext/src/org/jboss/tools/forge/runtime/ext/CtrlCAction.java:[8,0] [ERROR] import sun.misc.Signal; [ERROR] ^^^^^^^^^^^^^^^ [ERROR] Access restriction: The type Signal is not accessible due to restriction on classpath entry /usr/lib/jvm/java-6-openjdk/jre/lib/rt.jar To be clear with OSGi, the forge component has to provide a "framework extension bundle" to re-export these libs: see http://blog.meschberger.ch/2008/10/osgi-bundles-require-classes-from.html -- 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

12 years, 7 months

4
20
0 / 0

[JBoss JIRA] (JBIDE-10889) Ctrl+C stopped working in Forge Console

by Koen Aers (JIRA)

Koen Aers created JBIDE-10889: --------------------------------- Summary: Ctrl+C stopped working in Forge Console Key: JBIDE-10889 URL: https://issues.jboss.org/browse/JBIDE-10889 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Reporter: Koen Aers Assignee: Koen Aers Fix For: 3.3.0.Beta1 The sun.misc package needs to be imported by the module. -- 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

12 years, 7 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-10920) Forge: how to interrupt a command?

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-10920: ---------------------------------- Summary: Forge: how to interrupt a command? Key: JBIDE-10920 URL: https://issues.jboss.org/browse/JBIDE-10920 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: forge Affects Versions: 3.3.0.M5 Reporter: Pavol Srna Assignee: Koen Aers Fix For: 3.3.0.Beta1 How do I interrupt a "running" command? For example when I type: scaffold setup, then I want to interrupt the command. Is there a way how to do this? If not would it be possible to have this feature implemented? -- 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

12 years, 7 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2012