[JBoss JIRA] (JBIDE-21760) NPE is thrown on addition of a first pod-service mapping in Deploy docker image wizard
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21760?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21760:
--------------------------------
Fix Version/s: 4.3.1.CR1
> NPE is thrown on addition of a first pod-service mapping in Deploy docker image wizard
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-21760
> URL: https://issues.jboss.org/browse/JBIDE-21760
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: docker, openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: npe_docker.png
>
>
> In Deploy Docker Image wizard on 3rd wizard page, where service and pod port mapping is located, NPE is thrown when adding a new mapping and it is first (table displaying mapped service-pod is empty).
> !npe_docker.png!
> Stacktrace from error log:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.ServicePortDialog$PodPortValidator.validate(ServicePortDialog.java:154)
> at org.eclipse.core.databinding.UpdateValueStrategy.validateAfterConvert(UpdateValueStrategy.java:442)
> at org.eclipse.core.databinding.ValueBinding$3.run(ValueBinding.java:179)
> at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:150)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:154)
> at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:172)
> at org.eclipse.core.databinding.ValueBinding.doUpdate(ValueBinding.java:158)
> at org.eclipse.core.databinding.ValueBinding.access$4(ValueBinding.java:147)
> at org.eclipse.core.databinding.ValueBinding$1.handleValueChange(ValueBinding.java:46)
> at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:63)
> at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.fireValueChange(DecoratingObservableValue.java:57)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.handleValueChange(DecoratingObservableValue.java:99)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue$1.handleValueChange(DecoratingObservableValue.java:72)
> at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:63)
> at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119)
> at org.eclipse.core.databinding.observable.value.AbstractObservableValue.fireValueChange(AbstractObservableValue.java:74)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.notifyIfChanged(SimplePropertyObservableValue.java:127)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.access$2(SimplePropertyObservableValue.java:119)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$1$1.run(SimplePropertyObservableValue.java:69)
> at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:150)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:154)
> at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:172)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$1.handleEvent(SimplePropertyObservableValue.java:65)
> at org.eclipse.core.databinding.property.NativePropertyListener.fireChange(NativePropertyListener.java:65)
> at org.eclipse.jface.internal.databinding.swt.WidgetListener.handleEvent(WidgetListener.java:56)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.ServicePortDialog.open(ServicePortDialog.java:188)
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.ServicesAndRoutingPage$1.widgetSelected(ServicesAndRoutingPage.java:191)
> 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:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:257)
> at org.jboss.tools.openshift.internal.ui.handler.DeployImageHandler.execute(DeployImageHandler.java:58)
> 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:497)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> 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:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 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:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3598) Error while building Jboss developer studio 9.1.0 Beta 2 from source
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3598?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3598:
----------------------------------
Might actually need jar:file:/// if the zip isn't unpacked first.
> Error while building Jboss developer studio 9.1.0 Beta 2 from source
> --------------------------------------------------------------------
>
> Key: JBDS-3598
> URL: https://issues.jboss.org/browse/JBDS-3598
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.1.0.Beta2
> Environment: RHEL 7.1 PPC64le and Ubuntu x86_64
> Maven - 3.3.9
> JDK - 1.8
> Reporter: Deepali Chourasia
> Assignee: Nick Boldt
> Fix For: 9.1.0.CR1, 10.0.0.Alpha1
>
> Attachments: Jboss_devstudio_9.1.0_Beta2_buildlog.txt
>
>
> I have downloaded jboss-devstudio-9.1.0.Beta2-src.zip and am building it from source.
> The build fails with the following error:
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin (default-package-plugin) on project com.jboss.devstudio.core: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called. -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin (default-package-plugin) on project com.jboss.devstudio.core: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3598) Error while building Jboss developer studio 9.1.0 Beta 2 from source
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3598?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3598:
----------------------------------
To work around that would need to point the build at -Djbosstools-site=file:///path/to/Jbds-or-jbosstools/update/site/zip!/ or some equivalent location.
> Error while building Jboss developer studio 9.1.0 Beta 2 from source
> --------------------------------------------------------------------
>
> Key: JBDS-3598
> URL: https://issues.jboss.org/browse/JBDS-3598
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.1.0.Beta2
> Environment: RHEL 7.1 PPC64le and Ubuntu x86_64
> Maven - 3.3.9
> JDK - 1.8
> Reporter: Deepali Chourasia
> Assignee: Nick Boldt
> Fix For: 9.1.0.CR1, 10.0.0.Alpha1
>
> Attachments: Jboss_devstudio_9.1.0_Beta2_buildlog.txt
>
>
> I have downloaded jboss-devstudio-9.1.0.Beta2-src.zip and am building it from source.
> The build fails with the following error:
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin (default-package-plugin) on project com.jboss.devstudio.core: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called. -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin (default-package-plugin) on project com.jboss.devstudio.core: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBTIS-561) Add SwitchYard feature to Fuse category
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-561?page=com.atlassian.jira.plugin.... ]
Paul Leacu updated JBTIS-561:
-----------------------------
Attachment: fix.png
> Add SwitchYard feature to Fuse category
> ---------------------------------------
>
> Key: JBTIS-561
> URL: https://issues.jboss.org/browse/JBTIS-561
> Project: JBoss Tools Integration Stack
> Issue Type: Enhancement
> Components: distribution
> Affects Versions: 9.0.0.Beta1
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Attachments: fix.png
>
>
> Since there is only one product called JBoss Fuse which also includes SwitchYard I suggest to extend JBoss Fuse Development category by SwitchYard tooling. The category JBoss Integration and SOA Development can be removed (BPEL and BPMN2 modelers are installed together with SwitchYard tooling).
> If we extend the Fuse category then please extend com.jboss.devstudio.integration-stack.fuse.feature as well.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21763) Environment variables validation in deploy docker image wizard is not correct/consistent
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21763?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21763:
-----------------------------------------------
'Value' input is not validated because its content depends on the variable name.
So, in the error message we have only to replace 'value' with 'name' (or 'name value', but it would look redundant, and still may be confusing because of 'value' input on the same page).
Concerning validation of 'value', this reference https://developers.openshift.com/en/managing-environment-variables.html describes rules for values of some variables. Can we implement them as a feature? Could it be also of use to add to 'name' input content assist that would suggest these variable names? [~jcantrill], [~fbricon], what do you think?
> Environment variables validation in deploy docker image wizard is not correct/consistent
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-21763
> URL: https://issues.jboss.org/browse/JBIDE-21763
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: docker, openshift_v3
> Attachments: env_var_validation.png, invalid_env_var_value.png
>
>
> On 2nd page of Deploy Docker Image wizard is page containing environment variable. Dialog to create a new environment variable has a validation message but it is not correct, or at least validation message content does not fit reality. See following screenshots:
> First one is when entered invalid environment variable name. Notice message contains info about invalid value, not name, although it is name what is not valid.
> !env_var_validation.png!
> Second screeshoot displays so-called invalid value (regarding to validation message in first screenshot), but there is no validation error.
> !invalid_env_var_value.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month