[JBoss JIRA] (JBIDE-12693) New Openshift Application Wizard broken
by Radim Hopp (JIRA)
Radim Hopp created JBIDE-12693:
----------------------------------
Summary: New Openshift Application Wizard broken
Key: JBIDE-12693
URL: https://issues.jboss.org/browse/JBIDE-12693
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central, openshift
Affects Versions: 4.0.0.Alpha2
Reporter: Radim Hopp
Assignee: Snjezana Peco
Priority: Blocker
Fix For: 4.0.0.Alpha2
Currently is not possible to open New Openshift Application Wizard from JBoss Central.
NPE is thrown in Error Log:
{noformat}
java.lang.NullPointerException
at org.jboss.tools.openshift.express.internal.ui.wizard.GitCloningSettingsWizardPage.createCloneGroup(GitCloningSettingsWizardPage.java:194)
at org.jboss.tools.openshift.express.internal.ui.wizard.GitCloningSettingsWizardPage.doCreateControls(GitCloningSettingsWizardPage.java:92)
at org.jboss.tools.openshift.express.internal.ui.wizard.AbstractOpenShiftWizardPage.createControl(AbstractOpenShiftWizardPage.java:59)
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.setWizard(WizardDialog.java:1182)
at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1241)
at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1238)
at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1227)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1225)
at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:915)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
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:1276)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:259)
at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:279)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:76)
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:229)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:210)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:131)
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:171)
at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:492)
at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
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:3554)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.ui.internal.views.log.EventDetailsDialog.open(EventDetailsDialog.java:180)
at org.eclipse.ui.internal.views.log.EventDetailsDialogAction.run(EventDetailsDialogAction.java:98)
at org.eclipse.ui.internal.views.log.LogView$15.doubleClick(LogView.java:535)
at org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredViewer.java:845)
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.fireDoubleClick(StructuredViewer.java:843)
at org.eclipse.jface.viewers.AbstractTreeViewer.handleDoubleSelect(AbstractTreeViewer.java:1477)
at org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSelected(StructuredViewer.java:1246)
at org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEvent(OpenStrategy.java:249)
at org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.java:246)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:307)
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:3554)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1022)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:916)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:585)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:540)
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: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: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)
{noformat}
When trying to open New Openshift Application Wizard via File->New->Other->Openshift Application, the same NPE is thrown, but when I try to click "Next" one more time, wizard is opened.
--
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, 5 months
[JBoss JIRA] (JBIDE-12793) Wizard for addin Service implementations (ServiceLoader / Service file)
by Lincoln Baxter III (JIRA)
Lincoln Baxter III created JBIDE-12793:
------------------------------------------
Summary: Wizard for addin Service implementations (ServiceLoader / Service file)
Key: JBIDE-12793
URL: https://issues.jboss.org/browse/JBIDE-12793
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: Lincoln Baxter III
It would be very nice if we had a wizard for adding an existing class implemeting an interface to an the appropriate META-INF/services file, or creating said service file if it does not exist.
The user should probably be able to pick the interfaces to be used as service interfaces. (Either one or a time, or multiple at a time for convenience, not sure which would be easier to do.)
Cheers
--
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, 5 months
[JBoss JIRA] (JBIDE-12656) org.jboss.tools.jst.css.test.jbide.SelectionLosingByPropertySheet_JBIDE4791 failure
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-12656:
--------------------------------------
Summary: org.jboss.tools.jst.css.test.jbide.SelectionLosingByPropertySheet_JBIDE4791 failure
Key: JBIDE-12656
URL: https://issues.jboss.org/browse/JBIDE-12656
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 4.0.0.Alpha2
Reporter: Alexey Kazakov
Assignee: Yahor Radtsevich
Fix For: 4.0.0.Alpha2
{code}
testSelectionLosingByPropertySheet(org.jboss.tools.jst.css.test.jbide.SelectionLosingByPropertySheet_JBIDE4791) Time elapsed: 21.54 sec <<< FAILURE!
junit.framework.ComparisonFailure: expected:<red> but was:<null>
at junit.framework.Assert.assertEquals(Assert.java:85)
at junit.framework.Assert.assertEquals(Assert.java:91)
at org.jboss.tools.jst.css.test.jbide.SelectionLosingByPropertySheet_JBIDE4791.testSelectionLosingByPropertySheet(SelectionLosingByPropertySheet_JBIDE4791.java:94)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
{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, 5 months
[JBoss JIRA] (JBIDE-12791) UI Bug in Eclipse Juno caused by tools exception
by Nick Upton (JIRA)
Nick Upton created JBIDE-12791:
----------------------------------
Summary: UI Bug in Eclipse Juno caused by tools exception
Key: JBIDE-12791
URL: https://issues.jboss.org/browse/JBIDE-12791
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: Nick Upton
I was instructed to try here first on a UI bug in Eclipse. Here a few details:
When I open my project files in new tabs, files being opened for the first time display completely blank in the code screen. If I double click the tab to maximize, and repeat to minimize, the code then appears normally.
This happens consistently throughout my workday. I can close a file, open it again and it displays blank (grey background).
I am attaching the log files and a screenshot showing an exception in org.jboss.tools code.
-- Configuration Details --
Product: Eclipse 1.5.0.20120131-1544 (org.eclipse.epp.package.jee.product)
Installed Features:
org.eclipse.cvs 1.3.200.v20120525-1249-7B79FJJAkF7BF7SDL5EAJT
Windows 7 64-bit
--
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, 5 months
[JBoss JIRA] (JBIDE-12538) Configure Problem Severity should open project settings if they are enabled for the project
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-12538:
---------------------------------------------
Summary: Configure Problem Severity should open project settings if they are enabled for the project
Key: JBIDE-12538
URL: https://issues.jboss.org/browse/JBIDE-12538
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 3.3.0.Final
Reporter: Viacheslav Kabanovich
Assignee: Daniel Azarov
Fix For: 4.0.0.Alpha2
EXECUTE: Create CDI Project.
EXECUTE: Call project properties, select CDI Validator, and select 'Enable project specific settings'.
EXECUTE: Create an error, for example, an unsatisfied injection point.
EXECUTE: Call quick fix for warning.
ASSERT: Project Properties dialog appears, with selected preference.
Similar use-cases should be valid for other validators, not only CDI, since 'Configure Problem Severity' is a common feature.
--
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, 5 months
[JBoss JIRA] (JBIDE-12771) EclipseJavaUtil never evicts its cache when projects are deleted (or their classpath change)
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-12771:
-----------------------------------
Summary: EclipseJavaUtil never evicts its cache when projects are deleted (or their classpath change)
Key: JBIDE-12771
URL: https://issues.jboss.org/browse/JBIDE-12771
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 3.3.1
Reporter: Fred Bricon
Assignee: Alexey Kazakov
Fix For: 4.0.0.Beta1
When calling EclipseJavaUtil#findType(javaProject, qualifiedName) we hit a cache of ITypes using the project name has key.
Problem is, the cache is never updated if the project is deleted, or its classpath changes. This directly causes issues like JBIDE-12727, where we find an IType entry in a project's classpath which has the same name as a previously deleted project.
Everything is static in EclipseJavaUtil so we won't be able to implement IElementChangedListener directly. I believe you should had some new method in EclipseJavaUtil, like evict(key), that'd be called by an other IElementChangedListener, registered on plugin startup.
--
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, 5 months
[JBoss JIRA] (JBIDE-12741) CDI (and other JBT common validators) is disabled for workspace if you disable it for project
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-12741:
--------------------------------------
Summary: CDI (and other JBT common validators) is disabled for workspace if you disable it for project
Key: JBIDE-12741
URL: https://issues.jboss.org/browse/JBIDE-12741
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 4.0.0.Alpha2
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 4.0.0.Beta1
1. Open Window->Preferences->JBoss Tools->CDI->CDI Validator
2. Make sure it's enabled
3. Create a CDI project
4. Open project properties page
5. CDI->CDI Validator
6. Disable the validator for the project. Click Ok.
7. Open Window->Preferences->JBoss Tools->CDI->CDI Validator
8. FAILURE: The valdiator is disabled for the worspace too!
--
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, 5 months