[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:
------------------------------------------
PR to prevent the NPE when unknown build strategies are encountered: https://github.com/jbosstools/jbosstools-openshift/pull/1463
> 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)
9 years
[JBoss JIRA] (JBIDE-24129) download-devstudio profile breaks component builds
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24129?page=com.atlassian.jira.plugi... ]
Pavol Srna commented on JBIDE-24129:
------------------------------------
First, let me explain the reason why we need the profile and how we use it. We run integration tests against core devstudio (all plugins) even if the itests are only for e.g. hibernate (or other component) and verify it integrates well with the whole product. We saw some plugin collision problems in the past.
When tycho is about to run the itests it computes the target platform and installs com.jboss.devstudio.core.feature.feature.group from <devstudioRepository>https://devstudio.redhat.com/10.0/snapshots/updates/</devstudioRepository> into the running eclipse instance. This is defined in the download-devstudio profile. Then it installs itests and runs them.
This was completely fine and working when the itests have lived in integration-tests repository as a downstream project.The problem is when we move the itests into component repository and try to run them during the component build process.
As you can see from the error message in the description, {{_com.jboss.devstudio.core.feature.feature.group_}} depends on {{_org.jboss.ide.eclipse.as.feature.feature.group_}} and tycho doesn’t resolve the feature from site because we are building the as unit locally. What we would need is to resolve as.feature from site, install {{_com.jboss.devstudio.core.feature.feature.group_}} and then update the plugins with locally build plugins. This seems not to be supported by tycho.
We have two options how to approach the problem:
# itests run fine if you: cd into component/itests and run {code}mvn clean verify -PITests,download-devstudio{code} But will be disabled on component level by default.
# define all itests dependencies in MANIFEST. This has downsides.
a) the list can be long and tricky to maintain,
b) most likely it will create new dependencies for the component e.g. to m2e, to some other eclipse wizards (plugins) that the itests use, or to server adapter ui for end to end tests. Because integration tests have been designed as downstream devstudio project/component. Therefore they rely on e.g maven import, or server adapter (for the end to end tests) even if the component doesn’t have direct dependencies on these plugins.
[~jeffmaury] How would you like to come across the problem? Option 1) seems best to me.
> download-devstudio profile breaks component builds
> --------------------------------------------------
>
> Key: JBIDE-24129
> URL: https://issues.jboss.org/browse/JBIDE-24129
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, integration-tests
> Affects Versions: 4.4.4.AM2
> Reporter: Pavol Srna
> Assignee: Pavol Srna
> Priority: Critical
> Fix For: 4.4.4.AM3
>
>
> We have used download-devstudio profile to run the integration tests against full devstudio in the past. This stopped working recently.
> {code}
> [ERROR] Cannot resolve project dependencies:
> [ERROR] Software being installed: com.jboss.devstudio.core.feature.feature.group 10.4.0.v20170324-0935
> [ERROR] Missing requirement: com.jboss.devstudio.core.rpm.feature.feature.group 10.4.0.v20170324-0935 requires 'org.jboss.ide.eclipse.as.feature.feature.group [3.2.4.v20170315-1707]' but it could not be found
> [ERROR] Cannot satisfy dependency: com.jboss.devstudio.core.feature.feature.group 10.4.0.v20170324-0935 depends on: com.jboss.devstudio.core.rpm.feature.feature.group [10.4.0.v20170324-0935]
> [ERROR]
> [ERROR] See http://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting for help.
> [ERROR] Cannot resolve dependencies of MavenProject: org.jboss.tools.as.plugins:org.jboss.ide.eclipse.as.dmr:3.2.4-SNAPSHOT @ /Users/psrna/GitHub/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.dmr/pom.xml: See log for details -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MavenExecutionException
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24137) Improve robustness of DefaultConnectionProvider by ensuring connections attribute is initialized
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24137?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-24137:
-----------------------------------------
oh yes, need to be added to JMXCoreAllTests, I'm not used to TestSuite. I'm used to have test executed based on the Pattern Name.
> Improve robustness of DefaultConnectionProvider by ensuring connections attribute is initialized
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24137
> URL: https://issues.jboss.org/browse/JBIDE-24137
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: jmx
> Affects Versions: 4.4.4.AM1
> Reporter: Aurélien Pupier
> Assignee: Aurélien Pupier
> Priority: Minor
> Fix For: 4.4.4.AM2
>
>
> if addConnection is called before any getConnections, there is a NPE
> {noformat}
> java.lang.NullPointerException
> at org.jboss.tools.jmx.core.providers.DefaultConnectionProvider.addConnection(DefaultConnectionProvider.java:111)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBTIS-1082) SwitchYard specific updates to separate it from Fuse proper.
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-1082:
---------------------------------
Summary: SwitchYard specific updates to separate it from Fuse proper.
Key: JBTIS-1082
URL: https://issues.jboss.org/browse/JBTIS-1082
Project: JBoss Tools Integration Stack
Issue Type: Sub-task
Components: switchyard
Reporter: Paul Leacu
Assignee: Brian Fitzpatrick
Separate SwitchYard from Fuse Tooling proper. It should exist as a independent jar bundle.
Initial effort: - update to Oxygen JBTIS target platform
1. Modify that org.switchyard.tools.bpmn2.feature requirement to be org.eclipse.bpmn2.modeler.feature.group [1.3.0,1.4.0]
2. Pick up 4.5.0.AM1-SNAPSHOT as your JBTIS TP
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (ERT-479) Javascript Object's prototype property is not supported [EBZ#510677]
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/ERT-479?page=com.atlassian.jira.plugin.sy... ]
Victor Rubezhny reassigned ERT-479:
-----------------------------------
Assignee: Victor Rubezhny
> Javascript Object's prototype property is not supported [EBZ#510677]
> --------------------------------------------------------------------
>
> Key: ERT-479
> URL: https://issues.jboss.org/browse/ERT-479
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Assignee: Victor Rubezhny
> Labels: General, bzira
>
> As we get rid of complex model calculations and type inference in JSDT 2.0, we still have a need to support objects and their properties/functions defined via class prototype property in order to make it possible to correctly show/expand such properties/functions on the Outline as well as to propose/show them in content assistant, searching and for the validation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years