[JBoss JIRA] Created: (JBDS-1846) Runtime Detection Dialog during first start gets over modal dialog with request to let usage reporting.
by Andre Dietisheim (JIRA)
Runtime Detection Dialog during first start gets over modal dialog with request to let usage reporting.
-------------------------------------------------------------------------------------------------------
Key: JBDS-1846
URL: https://issues.jboss.org/browse/JBDS-1846
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: runtime, Usage Reporting
Affects Versions: 5.0.0.M3
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 5.0.0.M3
Request to let usage reporting modal dialog is opened first and then it is covered by bigger Runtime Detection Dilaog. Usage dialog is modal and nothing can be pressed and changed in Runtime Detection dialog. Sometimes I even didn't notice usage dialog and it was confusing because runtime detection dialog just didn't respond to mouse events.
There should be a way to show such dialogs one by one and not all at once blocking each other.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (JBIDE-2726) Incorrect behavior of Server properties > Ports Monitoring
by Aliaksey Nis (JIRA)
Incorrect behavior of Server properties > Ports Monitoring
----------------------------------------------------------
Key: JBIDE-2726
URL: https://jira.jboss.org/jira/browse/JBIDE-2726
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.alpha
Environment: WindowsXP SP2
JBoss Tools
Version: 3.0.0.Alpha1
Build id: 200809010011-nightly
Build date: 01 september 2008
JDK 1.5_08
Reporter: Aliaksey Nis
Priority: Optional
EXECUTE: Open Server view.
EXECUTE: Right click on Server > Properties.
EXECUTE: Select Monitoring. Press Add button.
EXECUTE: Add port number in "Monitor port". Try to select something from drop-down menu "Content".
FAILURE: Content menu is empty. But Ok button is enabled. When Ok button pressed - nothing happens (except wizard closing).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (JBIDE-4764) OpenOns don't work for xhtml pages with installed maven's plug-ins.
by Yura Zhishko (JIRA)
OpenOns don't work for xhtml pages with installed maven's plug-ins.
-------------------------------------------------------------------
Key: JBIDE-4764
URL: https://jira.jboss.org/jira/browse/JBIDE-4764
Project: JBoss Tools
Issue Type: Bug
Components: common, jsp/jsf/xml source editing, Visual Page Editor core
Affects Versions: 3.1.0.M3
Environment: Eclipse 3.5 win_32 with DTP, EMF, XSD, GEF, WTP plug-ins installed.
Maven plug-ins were installed from http://m2eclipse.sonatype.org/update/ update site (exclude Maven SCM handler for Subclipse and Maven Integration for AJDT)
JBT were installed from http://download.jboss.org/jbosstools/updates/nightly/trunk/ update site.
Reporter: Yura Zhishko
Assignee: Alexey Kazakov
Priority: Critical
1) Create new JSF kick start Project with Facelets
2) Open inputName.xhtml with JBossTools editor
3) Try to make Open-On on a "/templates/common.xhtml" link
RESULT: Nothing. Open-On doesn't work.
The possible reason is a conflict with Doxia Xhtml Editor. When we try to make Open-On in this editor an exception is thrown:
java.lang.AbstractMethodError
at org.eclipse.mylyn.internal.tasks.ui.TasksUiPlugin$11.run(TasksUiPlugin.java:1164)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.runtime.Platform.run(Platform.java:888)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.mylyn.internal.tasks.ui.TasksUiPlugin.getRepositoryForResource(TasksUiPlugin.java:1157)
at org.eclipse.mylyn.tasks.ui.AbstractTaskHyperlinkDetector.getTaskRepository(AbstractTaskHyperlinkDetector.java:166)
at org.eclipse.mylyn.tasks.ui.AbstractTaskHyperlinkDetector.getTaskRepositories(AbstractTaskHyperlinkDetector.java:130)
at org.eclipse.mylyn.internal.tasks.ui.editors.TaskHyperlinkDetector.detectHyperlinks(TaskHyperlinkDetector.java:38)
at org.eclipse.mylyn.tasks.ui.AbstractTaskHyperlinkDetector.detectHyperlinks(AbstractTaskHyperlinkDetector.java:93)
at org.eclipse.ui.texteditor.HyperlinkDetectorRegistry$HyperlinkDetectorDelegate.detectHyperlinks(HyperlinkDetectorRegistry.java:80)
at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:263)
at org.eclipse.jface.text.hyperlink.HyperlinkManager.mouseMove(HyperlinkManager.java:439)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:199)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
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:368)
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:585)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (JBIDE-9569) Remove VpeVisualDomBuilder.getNodeForUpdate rudiment method
by Maxim Areshkau (JIRA)
Remove VpeVisualDomBuilder.getNodeForUpdate rudiment method
-----------------------------------------------------------
Key: JBIDE-9569
URL: https://issues.jboss.org/browse/JBIDE-9569
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.3.0.M2
Reporter: Maxim Areshkau
Assignee: Yahor Radtsevich
Priority: Optional
For updating tables was added method VpeVisualDomBuilder.getNodeForUpdate which checks if element table-cell and if such returns parent. Such functionality implements template, so template for tr and td need to be updated and this rudiment method should be deleted.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months