[JBoss JIRA] (JBIDE-13931) Add LiveReload feature to Eclipse Marketplace?
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-13931:
----------------------------------
Summary: Add LiveReload feature to Eclipse Marketplace?
Key: JBIDE-13931
URL: https://issues.jboss.org/browse/JBIDE-13931
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: livereload, Marketplace
Affects Versions: 4.1.0.Alpha2
Reporter: Nick Boldt
Assignee: Nick Boldt
Should this feature be included in the list of features on the Eclipse Marketplace, or is it an "extra" thing that can be installed later?
--
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
13 years, 2 months
[JBoss JIRA] (JBIDE-13930) Generate source feature
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-13930:
----------------------------------
Summary: Generate source feature
Key: JBIDE-13930
URL: https://issues.jboss.org/browse/JBIDE-13930
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: livereload
Affects Versions: 4.1.0.Alpha2
Reporter: Nick Boldt
Assignee: Xavier Coulon
Need a source feature and plugin for this. Please generate one with Tycho.
--
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
13 years, 2 months
[JBoss JIRA] (JBIDE-13375) 6 test failures in org.jboss.tools.ws.creation.core.test.command.JBossWS*
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13375?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13375:
------------------------------------
Build #160 (Apr 4, 2013 7:06:27 PM) was successful (blue), including 440 tests (13 skipped). That's the same we had on June 4, 2012.
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> 6 test failures in org.jboss.tools.ws.creation.core.test.command.JBossWS*
> -------------------------------------------------------------------------
>
> Key: JBIDE-13375
> URL: https://issues.jboss.org/browse/JBIDE-13375
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Affects Versions: 3.3.2.Final
> Reporter: Nick Boldt
> Assignee: Brian Fitzpatrick
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_5.0.indigo/job/jbosstools-3.3_stable_branch.component--ws/156/testReport/}
> Test Result
> 6 failures (+6) , 13 skipped (±0)
> 440 tests (±0)
> Took 42 min.
> add description
> All Failed Tests
> Test Name Duration Age
> >>> org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest.testDeployResult 1 min 46 sec 1
> >>> org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest.testDeployResult 20 min 1
> >>> org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testInitialClientCommand 15 ms 1
> >>> org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testClientCodeGenerationCommand 7 ms 1
> >>> org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testRemoveClientJarsCommand 7 ms 1
> >>> org.jboss.tools.ws.creation.core.test.command.JBossWSMergeWebXMLCommandTest.testMergeWebXMLCommand 20 min 1{code}
--
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
13 years, 2 months
[JBoss JIRA] (JBIDE-13870) Can't re-add BrowserSim toolbar to perspective
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13870?page=com.atlassian.jira.plugi... ]
Michelle Murray commented on JBIDE-13870:
-----------------------------------------
A little more investigation - I have now tried this in Eclipse Juno (without JBT or JBDS installed) and it is an issue there. So, as rightly suggested, this is an Eclipse issue and not JBT or JBDS.
> Can't re-add BrowserSim toolbar to perspective
> ----------------------------------------------
>
> Key: JBIDE-13870
> URL: https://issues.jboss.org/browse/JBIDE-13870
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Visual Page Editor core
> Affects Versions: 4.0.0.Final
> Environment: Fedora 17, JBDS 6 standalone
> Reporter: Michelle Murray
> Assignee: Konstantin Marmalyukov
> Fix For: 4.1.0.Alpha2
>
>
> I removed the BrowserSim tool bar from the JBoss perspective and then tried to re-add it. But the check box was already selected, indicating it was already enabled, yet the toolbar still wasn't visible. I went back to JBDS 5 to see if it was a problem there to but it doesn't appear to be. This problem is not restricted to the JBoss perspective.
--
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
13 years, 2 months
[JBoss JIRA] (JBIDE-13856) Test jQuery Mobile Palette Wizards on different platforms
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13856?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-13856:
-----------------------------------------------
Recently failing on server tests NewJQueryMobilePaletteWizardTest and InsertJSCSSPaletteEntryTest fail because of this issue and configuration that does not allow to start neither Mozilla nor WebKit. Fix of this issue makes the tests independent of browser availability.
> Test jQuery Mobile Palette Wizards on different platforms
> ---------------------------------------------------------
>
> Key: JBIDE-13856
> URL: https://issues.jboss.org/browse/JBIDE-13856
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: jsp/jsf/xml/html source editing
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Fix For: 4.1.0.Alpha2
>
> Attachments: jbide-13856.patch, ubuntu_64_button.png, ubuntu_64_checkboxes.png, ubuntu_64_cjeckbox.png, ubuntu_64_collapsible.png, ubuntu_64_dialog.png, ubuntu_64_footerbar.png, ubuntu_64_grid.png, ubuntu_64_headerbar.png, ubuntu_64_large_font_toggle.png, ubuntu_64_link.png, ubuntu_64_listview.png, ubuntu_64_navbar.png, ubuntu_64_page.png, ubuntu_64_radio.png, ubuntu_64_slider.png, ubuntu_64_textinput.png, ubuntu_64_toggle.png
>
>
> If system font size is set to large, wizard should take it into account.
> For instance:
> !ubuntu_64_large_font_toggle.png!
> Windows 8 32bit (Eclipse+Java) Base+JST+VPE+Xulrunner + Safari:
> jQuery Mobile Palette Widget Wizards work fine.
> Windows 8 64bit (Eclipse+Java) Base+JST+VPE+Xulrunner + Safari:
> Wizards do not start
> {code}
> org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser])
> at org.eclipse.swt.SWT.error(SWT.java:4373)
> at org.eclipse.swt.SWT.error(SWT.java:4288)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4144)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1057)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:941)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:79)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> 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(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> 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: org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser]
> at org.eclipse.swt.SWT.error(SWT.java:4399)
> at org.eclipse.swt.browser.WebKit.create(WebKit.java:542)
> at org.eclipse.swt.browser.Browser.<init>(Browser.java:99)
> at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizardPage.createControl(AbstractNewHTMLWidgetWizardPage.java:139)
> at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174)
> at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608)
> at org.eclipse.jface.window.Window.create(Window.java:431)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104)
> at org.jboss.tools.common.model.ui.editors.dnd.DropWizardDialog.create(DropWizardDialog.java:95)
> at org.eclipse.jface.window.Window.open(Window.java:790)
> at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:110)
> at org.jboss.tools.jst.jsp.jspeditor.JSPTextEditor$4.run(JSPTextEditor.java:757)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 24 more
> {code}
> Windows 8 32 and 64 bits (Eclipse+Java) Base+JST + Safari:
> jQuery Mobile Palette Widget Wizards work without JavaScript.
> Windows 7 32 and 64 bits (Eclipse+Java) Base+JST + Safari:
> jQuery Mobile Palette Widget Wizards work without JavaScript.
> Windows 7 32 and 64 bit (Eclipse+Java) Base+JST+VPE+Xulrunner:
> jQuery Mobile Palette Widget Wizards work fine.
> Windows 7 32bit (Eclipse+Java) Base+JST+VPE+Xulrunner + Safari:
> jQuery Mobile Palette Widget Wizards work fine.
> Windows 7 32 and 64 bits (Eclipse+Java) Base+JST:
> Wizards do not start
> {code}
> org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser])
> at org.eclipse.swt.SWT.error(SWT.java:4392)
> at org.eclipse.swt.SWT.error(SWT.java:4307)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4145)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3762)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1108)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:992)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:137)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:600)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:555)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> 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: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: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: org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser]
> at org.eclipse.swt.SWT.error(SWT.java:4418)
> at org.eclipse.swt.browser.WebKit.create(WebKit.java:542)
> at org.eclipse.swt.browser.Browser.<init>(Browser.java:99)
> at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizardPage.createControl(AbstractNewHTMLWidgetWizardPage.java:139)
> at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174)
> at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608)
> at org.eclipse.jface.window.Window.create(Window.java:432)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104)
> at org.jboss.tools.common.model.ui.editors.dnd.DropWizardDialog.create(DropWizardDialog.java:95)
> at org.eclipse.jface.window.Window.open(Window.java:791)
> at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:110)
> at org.jboss.tools.jst.jsp.jspeditor.JSPTextEditor$4.run(JSPTextEditor.java:757)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 24 more
> {code}
> MacOs 64 bit (Eclipse+Java) Base+JST+VPE+Xulrunner:
> and
> MacOs 64 bit (Eclipse+Java) Base+JST:
> jQuery Mobile Palette Widget Wizards work fine.
--
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
13 years, 2 months
[JBoss JIRA] (JBIDE-13929) Cannot install m2 facet when jst.seam facet is missing
by Rob Cernich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13929?page=com.atlassian.jira.plugi... ]
Rob Cernich commented on JBIDE-13929:
-------------------------------------
A representative stack trace:
{noformat}
java.lang.ExceptionInInitializerError
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at org.eclipse.wst.common.project.facet.ui.internal.ProjectFacetsUiManagerImpl.create(ProjectFacetsUiManagerImpl.java:170)
at org.eclipse.wst.common.project.facet.ui.internal.ProjectFacetsUiManagerImpl.getWizardPages(ProjectFacetsUiManagerImpl.java:148)
at org.eclipse.wst.common.project.facet.ui.internal.ProjectFacetsUiManagerImpl.getWizardPages(ProjectFacetsUiManagerImpl.java:108)
at org.eclipse.wst.common.project.facet.ui.ProjectFacetsUiManager.getWizardPages(ProjectFacetsUiManager.java:30)
at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard.handleSelectedFacetsChangedEvent(ModifyFacetedProjectWizard.java:712)
at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard.createPageControls(ModifyFacetedProjectWizard.java:310)
at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736)
at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608)
at org.eclipse.jface.window.Window.create(Window.java:431)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089)
at org.eclipse.jface.window.Window.open(Window.java:790)
at org.switchyard.tools.ui.actions.SwitchYardSettingsAction.installSwitchYardFacet(SwitchYardSettingsAction.java:162)
at org.switchyard.tools.ui.actions.SwitchYardSettingsAction.internalRun(SwitchYardSettingsAction.java:103)
at org.switchyard.tools.ui.actions.SwitchYardSettingsAction.run(SwitchYardSettingsAction.java:76)
at org.eclipse.ui.actions.ActionDelegate.runWithEvent(ActionDelegate.java:70)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:241)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1276)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3562)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3186)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1045)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:940)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:587)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:542)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
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:353)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
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:629)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
Caused by: java.lang.IllegalArgumentException: Project facet jst.seam has not been defined.
at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectFrameworkImpl.getProjectFacet(FacetedProjectFrameworkImpl.java:234)
at org.eclipse.wst.common.project.facet.core.ProjectFacetsManager.getProjectFacet(ProjectFacetsManager.java:75)
at org.jboss.tools.maven.ui.internal.project.facet.MavenFacetInstallPage.<clinit>(MavenFacetInstallPage.java:64)
... 51 more
{noformat}
> Cannot install m2 facet when jst.seam facet is missing
> ------------------------------------------------------
>
> Key: JBIDE-13929
> URL: https://issues.jboss.org/browse/JBIDE-13929
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.0.0.Final
> Reporter: Rob Cernich
> Assignee: Fred Bricon
>
> An IllegalArgumentException is produced when loading MavenFacetInstallPage when the jst.seam facet is missing. One should be able to install the m2 facet regardless of whether or not seam tooling is installed.
> This is the line where the exception is thrown:
> public static final IProjectFacet SEAM_FACET = ProjectFacetsManager.getProjectFacet(SEAM_FACET_ID);
> This should be moved to a static init block to either catch the exception or check to see if the facet is defined first.
--
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
13 years, 2 months