[JBoss JIRA] (JBIDE-24232) New application wizard: NPE when trying to inspect defined resources for jenkins-pipeline-example
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24232?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-24232:
------------------------------------------
merged into jbosstools-4.4.x and cherry-picked into master
> New application wizard: NPE when trying to inspect defined resources for jenkins-pipeline-example
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24232
> URL: https://issues.jboss.org/browse/JBIDE-24232
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.4.4.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: application_wizard, openshift_v3, pipeline_build
> Fix For: 4.4.4.AM3
>
> Attachments: pipeline-buildconfig-entry.png
>
>
> steps:
> # ASSERT: use a cdk which has the "jenkins-pipeline-example" template
> # EXEC: launch the app wizard and in the list of available server templates select the "jenkins-pipeline-example" template
> # ASSERT: Details panel shows the details for this template and holds a button "Defined Resources..."
> # EXEC: hit the "Defined Resources..." button
> # ASSERT: Details dialog pops up listing all the resources
> # EXEC: click the 2nd build config "BuildConfig {sample-pipeline}"
> !pipeline-buildconfig-entry.png!
> Result:
> arrow (or +) to the left of the build config disappears, nothing else happens. In the Eclipse log you discover an NPE:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ResourceDetailsContentProvider.getBuildConfigChildren(ResourceDetailsContentProvider.java:93)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ResourceDetailsContentProvider.getChildren(ResourceDetailsContentProvider.java:49)
> at org.eclipse.jface.viewers.AbstractTreeViewer.getRawChildren(AbstractTreeViewer.java:1372)
> at org.eclipse.jface.viewers.TreeViewer.getRawChildren(TreeViewer.java:341)
> at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:907)
> at org.eclipse.jface.viewers.AbstractTreeViewer.getSortedChildren(AbstractTreeViewer.java:621)
> at org.eclipse.jface.viewers.AbstractTreeViewer.lambda$0(AbstractTreeViewer.java:817)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:795)
> at org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:596)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:766)
> at org.eclipse.jface.viewers.AbstractTreeViewer.handleTreeExpand(AbstractTreeViewer.java:1493)
> at org.eclipse.jface.viewers.TreeViewer.handleTreeExpand(TreeViewer.java:882)
> at org.eclipse.jface.viewers.AbstractTreeViewer$3.treeExpanded(AbstractTreeViewer.java:1505)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:133)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4256)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1524)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1509)
> at org.eclipse.swt.widgets.TreeItem.sendExpand(TreeItem.java:1050)
> at org.eclipse.swt.widgets.Tree.expandItem_expandChildren(Tree.java:1278)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5996)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:227)
> at org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1135)
> at org.eclipse.swt.widgets.Tree.mouseDownSuper(Tree.java:2102)
> at org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1127)
> at org.eclipse.swt.widgets.Control.mouseDown(Control.java:2624)
> at org.eclipse.swt.widgets.Tree.mouseDown(Tree.java:2069)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5733)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:227)
> at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2140)
> at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2402)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5797)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5226)
> at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5375)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
> at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3703)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceListPage$13.widgetSelected(ApplicationSourceListPage.java:590)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4256)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1524)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1509)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1313)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4080)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3706)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:287)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:270)
> at org.jboss.tools.openshift.internal.ui.handler.NewApplicationHandler.execute(NewApplicationHandler.java:34)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.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:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:488)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:433)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:454)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem$3.handleEvent(AbstractContributionItem.java:482)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4256)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1524)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1509)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1313)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4080)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3706)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:693)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months
[JBoss JIRA] (JBDS-4359) Two "Spring" folders in "New" wizard
by Lukáš Valach (JIRA)
Lukáš Valach created JBDS-4359:
----------------------------------
Summary: Two "Spring" folders in "New" wizard
Key: JBDS-4359
URL: https://issues.jboss.org/browse/JBDS-4359
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: central
Affects Versions: 10.4.0.AM3
Environment: Devstudio 10.4.0.AM3-v20170406-1058-B390 (installed form jar installer)
Reporter: Lukáš Valach
Priority: Minor
Fix For: 10.4.0.AM3
Attachments: Spring_in_New_wizard_2017-04-11_10-52-33.png
I noticed that after installation of "Spring IDE" from Red Hat Central -> Software/Update there are two folders named "Spring" in "New" wizard dialog (File -> New -> Other...).
!Spring_in_New_wizard_2017-04-11_10-52-33.png|thumbnail!
I think that these folders should be merged into one folder.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months
[JBoss JIRA] (JBDS-4357) Conflict org.eclipse.m2e.feature.feature.group 1.7.1.20161104-1805 vs 1.7.1.20170214-1514
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4357?page=com.atlassian.jira.plugin.... ]
Lukáš Valach commented on JBDS-4357:
------------------------------------
Devstudio 10.4. should uses these update sites:
|jboss.discovery.site.url\|devstudio\|10.4.0.AM3=|https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/latest/all/repo/
|jboss.discovery.earlyaccess.site.url\|devstudio\|10.4.0.AM3=|https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.earlyaccess_4.4.neon/latest/all/repo/
|jboss.discovery.site.integration-stack.url\|devstudio\|10.4.0.AM3=|https://devstudio.redhat.com/10.0/development/updates/integration-stack/discovery/
I opened these repositories in P2Browser and I see that they contains org.eclipse.m2e.feature.feature.group 1.7.1.20161104-1805 (oldest).
Automated test installs this feature using p2director, using this command:
{code:}
./eclipse -consolelog -console -debug -clean -application org.eclipse.equinox.p2.director -r https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.e... -i org.eclipse.m2e.feature.feature.group
{code}
Automated test passed because p2director installed 1.7.1.20170214-1514 (newer). I don't know where they found newer version than is in update site. I am getting the same results when I trying it on my PC. Please explain how it is possible, if you know.
----
The second thing, I noticed that in Help -> Installation details -> Configuration there aren't parameters from ide-config.properties, so I can't check if Devstudio uses proper update sites. Why they aren't there and where I could find them?
> Conflict org.eclipse.m2e.feature.feature.group 1.7.1.20161104-1805 vs 1.7.1.20170214-1514
> -----------------------------------------------------------------------------------------
>
> Key: JBDS-4357
> URL: https://issues.jboss.org/browse/JBDS-4357
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.4.0.AM3
> Environment: RHSCL: http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.4-RHEL-7-RC-1....
> Devstudio: 10.4-0.20170410.1402.el7
> OS: Fedora24 and RHEL7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 10.4.0.AM3
>
> Attachments: rh-eclipse46-devstudio10.4-0.20170410.1402.el7.log.20170410-1722_strict.txt
>
>
> I tried to install stuff form RH Central manually to verify if automated tests are reliable and I found this problem which automated test didn't catch.
> When I installed "JBoss Tools Maven Packaging Configurator" I got bundle exceptions related to org.eclipse.m2e.*, see the log:
> [^rh-eclipse46-devstudio10.4-0.20170410.1402.el7.log.20170410-1722_strict.txt]
> It seems that central contains org.eclipse.m2e 1.7.1.20161104-1805 but in Devstudio RPM is installed 1.7.1.20170214-1514.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months
[JBoss JIRA] (JBTIS-1085) Consider using a general project for testing Camel editor
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-1085:
----------------------------------------
Summary: Consider using a general project for testing Camel editor
Key: JBTIS-1085
URL: https://issues.jboss.org/browse/JBTIS-1085
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: Fuse IDE, QE
Affects Versions: 4.4.3.CR1
Reporter: Andrej Podhradsky
Assignee: Tomáš Sedmík
Consider using a general project for testing Camel editor as follows
1. Create a general project
2. File > New > Camel XML file
3. Do some basic operations such as editing Properties view
Note that this approach cannot replace all use cases related to the Camel editor since we still need to check whether proper dependencies were added to a maven project by adding a Canmel component, e.g. ActiveMQ.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months
[JBoss JIRA] (JBDS-4357) Conflict org.eclipse.m2e.feature.feature.group 1.7.1.20161104-1805 vs 1.7.1.20170214-1514
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4357?page=com.atlassian.jira.plugin.... ]
Lukáš Valach updated JBDS-4357:
-------------------------------
Summary: Conflict org.eclipse.m2e.feature.feature.group 1.7.1.20161104-1805 vs 1.7.1.20170214-1514 (was: Problem installing "JBoss Tools Maven Packaging Configurator")
> Conflict org.eclipse.m2e.feature.feature.group 1.7.1.20161104-1805 vs 1.7.1.20170214-1514
> -----------------------------------------------------------------------------------------
>
> Key: JBDS-4357
> URL: https://issues.jboss.org/browse/JBDS-4357
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.4.0.AM3
> Environment: RHSCL: http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.4-RHEL-7-RC-1....
> Devstudio: 10.4-0.20170410.1402.el7
> OS: Fedora24 and RHEL7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 10.4.0.AM3
>
> Attachments: rh-eclipse46-devstudio10.4-0.20170410.1402.el7.log.20170410-1722_strict.txt
>
>
> I tried to install stuff form RH Central manually to verify if automated tests are reliable and I found this problem which automated test didn't catch.
> When I installed "JBoss Tools Maven Packaging Configurator" I got bundle exceptions related to org.eclipse.m2e.*, see the log:
> [^rh-eclipse46-devstudio10.4-0.20170410.1402.el7.log.20170410-1722_strict.txt]
> It seems that central contains org.eclipse.m2e 1.7.1.20161104-1805 but in Devstudio RPM is installed 1.7.1.20170214-1514.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months