[JBoss JIRA] (JBDS-2857) Add OS X 10.9 Mavericks to the support matrix
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2857?page=com.atlassian.jira.plugin.... ]
Michelle Murray commented on JBDS-2857:
---------------------------------------
Thanks for the info and clarifications. I will update the supported configs doc on access.redhat with appropriate info at 7.1.1 release time.
> Add OS X 10.9 Mavericks to the support matrix
> ---------------------------------------------
>
> Key: JBDS-2857
> URL: https://issues.jboss.org/browse/JBDS-2857
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements
> Affects Versions: 7.1.0.CR1
> Reporter: Martin Malina
> Assignee: Len DiMaggio
> Fix For: 7.1.1.CR1, 8.0.0.Alpha2
>
>
> I know this comes very late, so you may want to just push this to 8.0.0 immediately.
> However, we've already been testing on Mavericks (I use it every day myself) since it was introduced on October 22, 2013 and have never seen any problem specific to it.
> I only realized we still don't have Mavericks in the matrix today when I checked Michelle's Supported Configurations document.
--
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, 2 months
[JBoss JIRA] (JBIDE-16417) Exceptions when "Configure->Add Arquilian Support ..." executed on broken maven project
by Denis Golovin (JIRA)
Denis Golovin created JBIDE-16417:
-------------------------------------
Summary: Exceptions when "Configure->Add Arquilian Support ..." executed on broken maven project
Key: JBIDE-16417
URL: https://issues.jboss.org/browse/JBIDE-16417
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: testing-tools
Reporter: Denis Golovin
Wizard fails to show preview on step 5 (see stacktrace below)
{code}java.lang.reflect.InvocationTargetException
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:422)
at org.eclipse.ltk.internal.ui.refactoring.RefactoringWizardDialog2.run(RefactoringWizardDialog2.java:331)
at org.eclipse.ltk.ui.refactoring.RefactoringWizard.createChange(RefactoringWizard.java:663)
at org.eclipse.ltk.ui.refactoring.RefactoringWizard.computeUserInputSuccessorPage(RefactoringWizard.java:502)
at org.eclipse.ltk.ui.refactoring.UserInputWizardPage.computeSuccessorPage(UserInputWizardPage.java:74)
at org.eclipse.ltk.ui.refactoring.UserInputWizardPage.getNextPage(UserInputWizardPage.java:114)
at org.eclipse.ltk.internal.ui.refactoring.RefactoringWizardDialog2.nextOrPreviewPressed(RefactoringWizardDialog2.java:497)
at org.eclipse.ltk.internal.ui.refactoring.RefactoringWizardDialog2.access$2(RefactoringWizardDialog2.java:494)
at org.eclipse.ltk.internal.ui.refactoring.RefactoringWizardDialog2$1.widgetSelected(RefactoringWizardDialog2.java:693)
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.Display.sendEvent(Display.java:4421)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3771)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3391)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
at org.eclipse.jface.window.Window.open(Window.java:803)
at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation$1.run(RefactoringWizardOpenOperation.java:187)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation.run(RefactoringWizardOpenOperation.java:202)
at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation.run(RefactoringWizardOpenOperation.java:122)
at org.jboss.tools.arquillian.ui.internal.commands.AddArquillianCommandHandler.execute(AddArquillianCommandHandler.java:48)
at org.jboss.tools.arquillian.ui.internal.commands.AddArquillianCommandHandler.execute(AddArquillianCommandHandler.java:38)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
at sun.reflect.GeneratedMethodAccessor83.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
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:163)
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:222)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:851)
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.Display.sendEvent(Display.java:4421)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3771)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3391)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:146)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:611)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:565)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:109)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:80)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:372)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:226)
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:606)
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.jboss.tools.arquillian.ui.internal.refactoring.AddArquillianSupportRefactoring.createChange(AddArquillianSupportRefactoring.java:154)
at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:124)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2346)
at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
Root exception:
java.lang.NullPointerException
at org.jboss.tools.arquillian.ui.internal.refactoring.AddArquillianSupportRefactoring.createChange(AddArquillianSupportRefactoring.java:154)
at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:124)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2346)
at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
{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
12 years, 2 months
[JBoss JIRA] (JBIDE-16387) jst.web.ui.test fails
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16387?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-16387:
----------------------------------------
I don't know how it's related but tests started failing after this commit - https://github.com/jbosstools/jbosstools-jst/pull/248
We need to investigate it.
> jst.web.ui.test fails
> ---------------------
>
> Key: JBIDE-16387
> URL: https://issues.jboss.org/browse/JBIDE-16387
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Alpha2
> Reporter: Daniel Azarov
> Assignee: Alexey Kazakov
> Fix For: 4.2.0.Alpha2
>
> Attachments: org.jboss.tools.jst.web.ui.test.JstWebUiAllTests.txt
>
>
> Tests in error:
> org.jboss.tools.jst.web.ui.openon.test.TaglibOpenOnTest(org.jboss.tools.test.util.ProjectImportTestSetup): Failed to execute runnable (java.lang.NullPointerException)
> org.jboss.tools.jst.web.ui.openon.test.CreateNewFileHyperlinkTest(org.jboss.tools.test.util.ProjectImportTestSetup): Failed to execute runnable (java.lang.NullPointerException)
> org.jboss.tools.jst.web.ui.openon.test.TaglibOpenOnTest(org.jboss.tools.test.util.ProjectImportTestSetup): Failed to execute runnable (java.lang.NullPointerException)
> org.jboss.tools.jst.web.ui.openon.test.CreateNewFileHyperlinkTest(org.jboss.tools.test.util.ProjectImportTestSetup): Failed to execute runnable (java.lang.NullPointerException)
--
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, 2 months
[JBoss JIRA] (JBIDE-16387) jst.web.ui.test fails
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16387?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-16387:
--------------------------------------
Assignee: Alexey Kazakov (was: Daniel Azarov)
> jst.web.ui.test fails
> ---------------------
>
> Key: JBIDE-16387
> URL: https://issues.jboss.org/browse/JBIDE-16387
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Alpha2
> Reporter: Daniel Azarov
> Assignee: Alexey Kazakov
> Fix For: 4.2.0.Alpha2
>
> Attachments: org.jboss.tools.jst.web.ui.test.JstWebUiAllTests.txt
>
>
> Tests in error:
> org.jboss.tools.jst.web.ui.openon.test.TaglibOpenOnTest(org.jboss.tools.test.util.ProjectImportTestSetup): Failed to execute runnable (java.lang.NullPointerException)
> org.jboss.tools.jst.web.ui.openon.test.CreateNewFileHyperlinkTest(org.jboss.tools.test.util.ProjectImportTestSetup): Failed to execute runnable (java.lang.NullPointerException)
> org.jboss.tools.jst.web.ui.openon.test.TaglibOpenOnTest(org.jboss.tools.test.util.ProjectImportTestSetup): Failed to execute runnable (java.lang.NullPointerException)
> org.jboss.tools.jst.web.ui.openon.test.CreateNewFileHyperlinkTest(org.jboss.tools.test.util.ProjectImportTestSetup): Failed to execute runnable (java.lang.NullPointerException)
--
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, 2 months
[JBoss JIRA] (JBIDE-16298) Layout for BrowserSim/CordovaSim Preferences should look similar to JRE tab in Java Application Run Configuration
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16298?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-16298:
-----------------------------------
Fix Version/s: 4.2.0.Beta1
> Layout for BrowserSim/CordovaSim Preferences should look similar to JRE tab in Java Application Run Configuration
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16298
> URL: https://issues.jboss.org/browse/JBIDE-16298
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.1.1.Final
> Reporter: Denis Golovin
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.0.Beta1
>
> Attachments: Selection_023.png, Selection_024.png
>
>
> BrowserSim/CordovaSim Preferences should look very close to Java Application Launcher JRE configuration in Run Configuration Dialog:
> !Selection_024.png!
> Now it looks like:
> !Selection_023.png!
> What should be changed:
> 1. Group label should be "JRE to run BrowserSim/CordovaSim"
> 2. First radio button should use lable "Workspace Default JRE (jre-name-from-installed)
> 3. Second radio should be labeled as "Alternate JRE:"
> 4. Combo box with available JRE's should be placed right after "Alternate JRE:' label
> 5. Description text "See 'Installed JREs' for JRE definitions" should be replaced with ''General settings for BrowserSim/CordovaSim."
> 6. Add 'Installed JREs...' after combo box
--
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, 2 months
[JBoss JIRA] (JBIDE-16298) Layout for BrowserSim/CordovaSim Preferences should look similar to JRE tab in Java Application Run Configuration
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16298?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-16298:
--------------------------------------
Assignee: Konstantin Marmalyukov
> Layout for BrowserSim/CordovaSim Preferences should look similar to JRE tab in Java Application Run Configuration
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16298
> URL: https://issues.jboss.org/browse/JBIDE-16298
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.1.1.Final
> Reporter: Denis Golovin
> Assignee: Konstantin Marmalyukov
> Attachments: Selection_023.png, Selection_024.png
>
>
> BrowserSim/CordovaSim Preferences should look very close to Java Application Launcher JRE configuration in Run Configuration Dialog:
> !Selection_024.png!
> Now it looks like:
> !Selection_023.png!
> What should be changed:
> 1. Group label should be "JRE to run BrowserSim/CordovaSim"
> 2. First radio button should use lable "Workspace Default JRE (jre-name-from-installed)
> 3. Second radio should be labeled as "Alternate JRE:"
> 4. Combo box with available JRE's should be placed right after "Alternate JRE:' label
> 5. Description text "See 'Installed JREs' for JRE definitions" should be replaced with ''General settings for BrowserSim/CordovaSim."
> 6. Add 'Installed JREs...' after combo box
--
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, 2 months