[JBoss JIRA] (TOOLSDOC-380) Technical Review of 7.0 Installation Guide
by Michelle Murray (JIRA)
Michelle Murray created TOOLSDOC-380:
----------------------------------------
Summary: Technical Review of 7.0 Installation Guide
Key: TOOLSDOC-380
URL: https://issues.jboss.org/browse/TOOLSDOC-380
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Installation Guide
Affects Versions: 4.1.0
Reporter: Michelle Murray
Assignee: Michelle Murray
Fix For: 4.1.0
Conduct a post release technical review of 7.0 Installation Guide to catch any previously missed technical or copy errors.
--
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
12 years, 8 months
[JBoss JIRA] (TOOLSDOC-379) Technical Review of 7.0 Guides
by Michelle Murray (JIRA)
Michelle Murray created TOOLSDOC-379:
----------------------------------------
Summary: Technical Review of 7.0 Guides
Key: TOOLSDOC-379
URL: https://issues.jboss.org/browse/TOOLSDOC-379
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Task
Security Level: Public (Everyone can see)
Components: General documentation issues
Affects Versions: 4.1.0
Reporter: Michelle Murray
Assignee: Michelle Murray
Fix For: 4.1.0
Conduct a post release technical review of 7.0 docs to catch any previously missed technical or copy errors.
--
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
12 years, 8 months
[JBoss JIRA] (JBIDE-14849) Exceptions when working with font-family in CSS Dialog
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14849?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-14849:
---------------------------------------
it is marked as fixed, but after I got master branch and ran it locally, I can confirm it is still not fixed. Updated bugzilla with new stacktrace and test scenario to replicate
> Exceptions when working with font-family in CSS Dialog
> ------------------------------------------------------
>
> Key: JBIDE-14849
> URL: https://issues.jboss.org/browse/JBIDE-14849
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, upstream
> Affects Versions: 4.1.0.Beta2
> Reporter: Alexey Kazakov
> Assignee: Denis Golovin
> Fix For: 4.1.x
>
>
> I have a copy of jquery.mobile-1.3.0.css in one of my projects.
> I opened it with the default editor and then opened CSS Dialog.
> The I got the following exceptions it the log:
> {code}
> org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:63)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:850)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:743)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:727)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:662)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> 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:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> Caused by: java.lang.NullPointerException
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocumentRegion.getText(BasicStructuredDocumentRegion.java:304)
> at org.eclipse.wst.css.core.internal.document.CSSDeclarationItemParser.getText(CSSDeclarationItemParser.java:1073)
> at org.eclipse.wst.css.core.internal.document.CSSDeclarationItemParser.createPrimitiveValue(CSSDeclarationItemParser.java:364)
> at org.eclipse.wst.css.core.internal.document.CSSDeclarationItemParser.setupValues(CSSDeclarationItemParser.java:1014)
> at org.eclipse.wst.css.core.internal.document.CSSDeclarationItemParser.setupValues(CSSDeclarationItemParser.java:964)
> at org.eclipse.wst.css.core.internal.document.CSSStyleDeclItemImpl.setCssValueTextCore(CSSStyleDeclItemImpl.java:260)
> at org.eclipse.wst.css.core.internal.document.CSSStyleDeclItemImpl.setCssValueText(CSSStyleDeclItemImpl.java:234)
> at org.eclipse.wst.css.core.internal.document.CSSStyleDeclarationImpl.setProperty(CSSStyleDeclarationImpl.java:267)
> at org.jboss.tools.jst.css.dialog.common.CSSModel.updateCSSStyle(CSSModel.java:297)
> at org.jboss.tools.jst.css.dialog.CSSClassDialog.handleSelectorSwitched(CSSClassDialog.java:250)
> at org.jboss.tools.jst.css.dialog.CSSClassDialog$1.modifyText(CSSClassDialog.java:152)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:179)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1416)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1397)
> at org.eclipse.swt.widgets.Combo.select(Combo.java:1726)
> at org.jboss.tools.jst.css.dialog.CSSClassDialog.updateControlPane(CSSClassDialog.java:377)
> at org.jboss.tools.jst.css.dialog.CSSClassDialog.createContents(CSSClassDialog.java:99)
> at org.eclipse.jface.window.Window.create(Window.java:432)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104)
> at org.eclipse.jface.window.Window.open(Window.java:791)
> at org.jboss.tools.jst.css.dialog.OpenCSSDialogActionDelegate.run(OpenCSSDialogActionDelegate.java:70)
> at org.eclipse.ui.internal.handlers.ActionDelegateHandlerProxy.execute(ActionDelegateHandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> ... 37 more
> {code}
> Dialog is not opened.
> If you try to open it again you will get an empty error message in the log:
> {code}
> !ENTRY org.jboss.tools.jst.css 4 0 2013-06-12 14:27:10.147
> !MESSAGE
> {code}
> The dialog is opened.
> Click on OK and get another exception:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.jst.css.dialog.common.CSSModel.save(CSSModel.java:260)
> at org.jboss.tools.jst.css.dialog.CSSClassDialog.save(CSSClassDialog.java:295)
> at org.jboss.tools.jst.css.dialog.CSSClassDialog.close(CSSClassDialog.java:315)
> at org.eclipse.jface.dialogs.Dialog.okPressed(Dialog.java:955)
> at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:476)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:826)
> at org.eclipse.jface.window.Window.open(Window.java:802)
> at org.jboss.tools.jst.css.dialog.OpenCSSDialogActionDelegate.run(OpenCSSDialogActionDelegate.java:70)
> at org.eclipse.ui.internal.handlers.ActionDelegateHandlerProxy.execute(ActionDelegateHandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:850)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:743)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:727)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:662)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> 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:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
> The dialog is not closed.
> Didn't try another CSS file.
--
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
12 years, 8 months
[JBoss JIRA] (JBIDE-15263) Create Datasource Dialog/Wizard usability
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15263?page=com.atlassian.jira.plugi... ]
Burr Sutter commented on JBIDE-15263:
-------------------------------------
Yes! :-)
> Create Datasource Dialog/Wizard usability
> -----------------------------------------
>
> Key: JBIDE-15263
> URL: https://issues.jboss.org/browse/JBIDE-15263
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: common/jst/core
> Affects Versions: 4.1.0.Beta2
> Reporter: Burr Sutter
> Assignee: Viacheslav Kabanovich
> Fix For: 4.2.0.Alpha1
>
> Attachments: 2013-07-19_1034.png
>
>
> The current Create Datasource dialog has a few usability "gotchas":
> 1) It is located under the "JBoss Tools Web" category - when it is more appropriate to be under the "JBoss Tools" category, closer to the Forge wizards - where you need it.
> 2) It defaults to AS5, not AS7 - it should default to EAP6/AS7
> 3) It defaults to register in persistence.xml - it is unclear to me how cleanly this injects into the current persistence.xml provided by the Forge wizards, I tend to uncheck it to be safe - then manually tweak up the persistence.xml to reference the same resource.
--
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
12 years, 8 months
[JBoss JIRA] (JBIDE-15286) Increment service version of jbosstools-base/usage submodule
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15286?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-15286:
---------------------------------------
it cannot be 1.2.2. There should be gap between current released version from 4.1.x stream and version in next dev stream, so we would be able to release update to 1.2.1 only. according to:
{quote}When to change the service segment
The service segment number must be incremented whenever there have been changes to a plug-in between releases that are not visible in its API. For example, a bug has been fixed in the code, the plug-in manifest has changed, documentation has changed, compiler settings have changed. In general, if that change happens in a service (a.k.a. maintenance) release, then 1 is added. If it happens for the next official release, 100 has to be added. As a result, the service segment number for official releases normally ends with a zero (0, 100, 200, etc.). If that is not true for whatever reason, then one must not add 100 but instead set the service segment number to the next number that is divisible by 100, so that the normal numbering scheme is restored. This practice makes it easy to manage one line of descent after a release and still guarantee that plug-ins coming in the next release will have a higher version number than ones from maintenance releases (thus enabling the usage of update manager from maintenance releases to the new releases).{quote}
new version in dev N+1 stream should be 1.2.100. Then if we need deliver update for 4.1.0 as 4.1.1.Final usage would get updated version 1.2.2, which means this update could be installed only for 4.1.0.Final, but not for 4.2.0 stream where usage version is 1.2.100, because 1.2.1<1.2.2<1.2.100.
> Increment service version of jbosstools-base/usage submodule
> ------------------------------------------------------------
>
> Key: JBIDE-15286
> URL: https://issues.jboss.org/browse/JBIDE-15286
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: usage
> Affects Versions: 4.2.0.Alpha1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.2.0.Alpha1
>
>
> Internal classes only were changed since creating 4.1.x branch. Service version should be changed from 1.2.1 to 1.2.100 according http://wiki.eclipse.org/Version_Numbering.
--
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
12 years, 8 months
[JBoss JIRA] (JBIDE-4523) Visual Page Editor doesn't work with Eclipse with OSX Cocoa 64-bit (32-bit already fixed)
by Yahor Radtsevich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-4523?page=com.atlassian.jira.plugin... ]
Yahor Radtsevich updated JBIDE-4523:
------------------------------------
Fix Version/s: 4.2.x
(was: 4.1.x)
> Visual Page Editor doesn't work with Eclipse with OSX Cocoa 64-bit (32-bit already fixed)
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-4523
> URL: https://issues.jboss.org/browse/JBIDE-4523
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Visual Page Editor core
> Affects Versions: 3.1.0.M1
> Environment: Mac OSX 10.5.7, Eclipse 3.5 JEE Cocoa, JBoss Tools 3.1.0.M1
> Reporter: César Pérez
> Assignee: Yahor Radtsevich
> Labels: cocoa, new_and_noteworthy, osx, vpe
> Fix For: 4.2.x
>
>
> The Visual Page Editor does not work under the final version of Eclipse 3.5 JEE Cocoa for Mac OSX and JBoss Tools 3.1.0.M1, the error is due to a missing cocoa version of XUL runner as you can see in the following stacktrace:
> org.jboss.tools.vpe.xulrunner.XulRunnerException: Bundle org.mozilla.xulrunner.cocoa.macosx is not found.
> at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.getXulRunnerPath(XulRunnerBrowser.java:219)
> at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.initXulRunner(XulRunnerBrowser.java:114)
> at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.<init>(XulRunnerBrowser.java:85)
> at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.<init>(XulRunnerEditor.java:135)
> at org.jboss.tools.vpe.editor.mozilla.MozillaPreview$1.<init>(MozillaPreview.java:59)
> at org.jboss.tools.vpe.editor.mozilla.MozillaPreview.createPartControl(MozillaPreview.java:59)
> at org.jboss.tools.vpe.editor.VpeEditorPart.createPreviewBrowser(VpeEditorPart.java:921)
> at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:248)
> at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart$2.widgetSelected(JSPMultiPageEditorPart.java:106)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:3542)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1247)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1270)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1255)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1076)
> at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3256)
> at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:2045)
> at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:323)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:3542)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1247)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1270)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1255)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1076)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3440)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3099)
> 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)
--
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
12 years, 8 months
[JBoss JIRA] (JBIDE-4523) Visual Page Editor doesn't work with Eclipse with OSX Cocoa 64-bit (32-bit already fixed)
by Yahor Radtsevich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-4523?page=com.atlassian.jira.plugin... ]
Yahor Radtsevich updated JBIDE-4523:
------------------------------------
Summary: Visual Page Editor doesn't work with Eclipse with OSX Cocoa 64-bit (32-bit already fixed) (was: Visual Page Editor doesn't work with Eclipse 3.5 OSX Cocoa)
> Visual Page Editor doesn't work with Eclipse with OSX Cocoa 64-bit (32-bit already fixed)
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-4523
> URL: https://issues.jboss.org/browse/JBIDE-4523
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Visual Page Editor core
> Affects Versions: 3.1.0.M1
> Environment: Mac OSX 10.5.7, Eclipse 3.5 JEE Cocoa, JBoss Tools 3.1.0.M1
> Reporter: César Pérez
> Assignee: Yahor Radtsevich
> Labels: cocoa, new_and_noteworthy, osx, vpe
> Fix For: 4.1.x
>
>
> The Visual Page Editor does not work under the final version of Eclipse 3.5 JEE Cocoa for Mac OSX and JBoss Tools 3.1.0.M1, the error is due to a missing cocoa version of XUL runner as you can see in the following stacktrace:
> org.jboss.tools.vpe.xulrunner.XulRunnerException: Bundle org.mozilla.xulrunner.cocoa.macosx is not found.
> at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.getXulRunnerPath(XulRunnerBrowser.java:219)
> at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.initXulRunner(XulRunnerBrowser.java:114)
> at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.<init>(XulRunnerBrowser.java:85)
> at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.<init>(XulRunnerEditor.java:135)
> at org.jboss.tools.vpe.editor.mozilla.MozillaPreview$1.<init>(MozillaPreview.java:59)
> at org.jboss.tools.vpe.editor.mozilla.MozillaPreview.createPartControl(MozillaPreview.java:59)
> at org.jboss.tools.vpe.editor.VpeEditorPart.createPreviewBrowser(VpeEditorPart.java:921)
> at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:248)
> at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart$2.widgetSelected(JSPMultiPageEditorPart.java:106)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:3542)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1247)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1270)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1255)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1076)
> at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3256)
> at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:2045)
> at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:323)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:3542)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1247)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1270)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1255)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1076)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3440)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3099)
> 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)
--
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
12 years, 8 months