[JBoss JIRA] (JBIDE-19323) java.lang.NullPointerException and no results after HQL query execution when JDBC sting is incorrect
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19323?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-19323:
------------------------------
Fix Version/s: 4.4.2.Final
> java.lang.NullPointerException and no results after HQL query execution when JDBC sting is incorrect
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19323
> URL: https://issues.jboss.org/browse/JBIDE-19323
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.3.0.Alpha1
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Fix For: 4.4.2.Final
>
>
> There should be some more user friendly message, not just NPE when JDBC string is not correct
> {code}
> !ENTRY org.eclipse.ui 4 0 2015-02-19 10:39:33.217
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.lang.NullPointerException
> at org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1886)
> at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1843)
> at org.jboss.tools.hibernate.proxy.ConfigurationProxy.buildSessionFactory(ConfigurationProxy.java:117)
> at org.hibernate.console.ConsoleConfiguration$5.execute(ConsoleConfiguration.java:285)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
> at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:280)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.execute(ExecuteQueryAction.java:81)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.run(ExecuteQueryAction.java:55)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.runWithEvent(ExecuteQueryAction.java:59)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:462)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4480)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1413)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3818)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3428)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:648)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:592)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.jboss.reddeer.eclipse.core.UITestApplication.start(UITestApplication.java:47)
> 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:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-19323) java.lang.NullPointerException and no results after HQL query execution when JDBC sting is incorrect
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19323?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-19323:
------------------------------
Fix Version/s: (was: 4.4.2.AM3)
> java.lang.NullPointerException and no results after HQL query execution when JDBC sting is incorrect
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19323
> URL: https://issues.jboss.org/browse/JBIDE-19323
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.3.0.Alpha1
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Fix For: 4.4.2.Final
>
>
> There should be some more user friendly message, not just NPE when JDBC string is not correct
> {code}
> !ENTRY org.eclipse.ui 4 0 2015-02-19 10:39:33.217
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.lang.NullPointerException
> at org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1886)
> at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1843)
> at org.jboss.tools.hibernate.proxy.ConfigurationProxy.buildSessionFactory(ConfigurationProxy.java:117)
> at org.hibernate.console.ConsoleConfiguration$5.execute(ConsoleConfiguration.java:285)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
> at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:280)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.execute(ExecuteQueryAction.java:81)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.run(ExecuteQueryAction.java:55)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.runWithEvent(ExecuteQueryAction.java:59)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:462)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4480)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1413)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3818)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3428)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:648)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:592)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.jboss.reddeer.eclipse.core.UITestApplication.start(UITestApplication.java:47)
> 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:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23149) Reverse engineering strategy cannot be set to custom class if generation target is Hibernate 5.x
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23149?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-23149:
------------------------------
Sprint: devex #123 November 2016 (was: devex #122 October 2016)
> Reverse engineering strategy cannot be set to custom class if generation target is Hibernate 5.x
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23149
> URL: https://issues.jboss.org/browse/JBIDE-23149
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.4.0.Final
> Reporter: Antal Varga
> Assignee: Koen Aers
> Fix For: 4.4.2.AM3
>
> Attachments: BaseReverseEngineeringStrategy.java, RMAReverseEngineeringStrategy.java
>
>
> The reason for that is the change in ServiceImpl.java in org.jboss.tools.hibernate.runtime.v_5_0*.jar or later.
> private Object newReverseEngineeringStrategy(String className, Object delegate) {...}
> tries to load class using the class loader of the delegate object at first which is *org.hibernate.cfg.reveng.OverrideRepository* and resides in *hibernate-tools-x.yy.jar*.
> The main problem is that while in case of the earlier Hibernate generation targets (e.g. 4.3) the reverse engineering strategy class loading was done by *org.hibernate.util.xpl.ReflectHelper* (and worked well), this option
> happens only as a fallback case now *BUT this only happens if the constructor has not been found* (only NoSuchMethodException is caught).
> Therefore a reverse engineering strategy can only be loaded if it is loaded by the classloader of the hibernate-tools-x.yy.jar or one of its parent loaders (OSGI can make the things more complicated).
> *I think the solution would be to catch ClassNotFoundException as well and try to load reverse engineering class using ReflectHelper in this case.*
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23066) Generating hbm.xml files always happens using the 3.5 runtime
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23066?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-23066:
------------------------------
Sprint: devex #123 November 2016 (was: devex #122 October 2016)
> Generating hbm.xml files always happens using the 3.5 runtime
> -------------------------------------------------------------
>
> Key: JBIDE-23066
> URL: https://issues.jboss.org/browse/JBIDE-23066
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.4.1.Final
> Reporter: Koen Aers
> Assignee: Koen Aers
> Fix For: 4.4.2.AM3
>
>
> This issue is related to JBIDE-22997 and JBIDE-23059. After implementing JBIDE-23059 the phenomenon described in JBIDE-22997 disappeared but the hbm.xml files are now always generated using the 3.5 runtime, even when the project is a hibernate project with a console configuration using another version.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-8371) Query Parameters View: apply parameter value on focus lost
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-8371?page=com.atlassian.jira.plugin... ]
Koen Aers updated JBIDE-8371:
-----------------------------
Sprint: devex #123 November 2016 (was: devex #122 October 2016)
> Query Parameters View: apply parameter value on focus lost
> ----------------------------------------------------------
>
> Key: JBIDE-8371
> URL: https://issues.jboss.org/browse/JBIDE-8371
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 3.2.0.CR1
> Reporter: Dmitry Geraskov
> Assignee: Koen Aers
> Fix For: 4.4.2.AM3
>
>
> Test case:
> 1. create query in HQL Editor:
> from test.Message m where m.id = :id
> 2. propulate the parameter in Parameters view
> 3. change type to valid(integer)
> 4. enter the value, but do not press Enter
> 5. Run the query.
> The value is not applied and considered as null.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-19323) java.lang.NullPointerException and no results after HQL query execution when JDBC sting is incorrect
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19323?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-19323:
------------------------------
Sprint: devex #123 November 2016 (was: devex #122 October 2016)
> java.lang.NullPointerException and no results after HQL query execution when JDBC sting is incorrect
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19323
> URL: https://issues.jboss.org/browse/JBIDE-19323
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.3.0.Alpha1
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Fix For: 4.4.2.AM3
>
>
> There should be some more user friendly message, not just NPE when JDBC string is not correct
> {code}
> !ENTRY org.eclipse.ui 4 0 2015-02-19 10:39:33.217
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.lang.NullPointerException
> at org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1886)
> at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1843)
> at org.jboss.tools.hibernate.proxy.ConfigurationProxy.buildSessionFactory(ConfigurationProxy.java:117)
> at org.hibernate.console.ConsoleConfiguration$5.execute(ConsoleConfiguration.java:285)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
> at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:280)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.execute(ExecuteQueryAction.java:81)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.run(ExecuteQueryAction.java:55)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.runWithEvent(ExecuteQueryAction.java:59)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:462)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4480)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1413)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3818)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3428)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:648)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:592)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.jboss.reddeer.eclipse.core.UITestApplication.start(UITestApplication.java:47)
> 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:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23177) Server Editor: Combo items have wrong size
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23177?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-23177 at 11/7/16 5:22 AM:
-------------------------------------------------------------------
I think that I also just experienced the issue. See the screenshot below:
!eclipse-project-overlaps-browse.png!
I run FC23/gtk3-3.18.9-1.fc23.x86_64
was (Author: adietish):
I think that I also just experienced the issue. See the screenshot below:
!eclipse-project-overlaps-browse.png!
I run FC23/eclipse-project-overlaps-browse.png
> Server Editor: Combo items have wrong size
> ------------------------------------------
>
> Key: JBIDE-23177
> URL: https://issues.jboss.org/browse/JBIDE-23177
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM1
> Reporter: Marián Labuda
> Assignee: Snjezana Peco
> Labels: openshift_v3, server_editor
> Fix For: 4.4.2.Final
>
> Attachments: combos.png, eclipse-project-overlaps-browse.png
>
>
> When I open an OpenShift 3 Server Editor the combo boxes have weird size, there are overlapping widgets.
> !combos.png!
> Spotted on Fedora 24 with GTK 3.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23352) Deploy Docker Wizard: Default routing port selection need more info for users
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23352?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23352:
------------------------------------------
[~jeffmaury] [~fbricon] Can you please reiterate the reasoning for offering to add/remove/edit ports in the Deploy Docker Image wizard/"Services & Routing Settings" wizard page?
We're thinking about removing these abilities.
> Deploy Docker Wizard: Default routing port selection need more info for users
> -----------------------------------------------------------------------------
>
> Key: JBIDE-23352
> URL: https://issues.jboss.org/browse/JBIDE-23352
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.2.Final
>
> Attachments: no_route_selected.png, refdoc-services-1.png, refdoc-services-2.png, webui-deploy-docker-image.png
>
>
> In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default , but OpenShift knows what to open.
> If there is only one port mapping, we could check it by default. If there are more port mappings, we could show a label/info/description what is gonna be done under the hood, so users will know what is happening.
> steps to reproduce:
> # EXEC: In Docker Explroer: pick an image and choose "Deploy to OpenShift..." in the context menu
> # EXEC: get to the "Services & Routing Settings" page
> !no_route_selected.png!
> It's not obvious to the user what the wizard will create: A service that "exposes" pod ports and a route that points to this service. Furthermore it's not obvious that without a "checked" (used by route) port, the route will round-robin through the available ports. Additionally we should show the user what ports are exposed by the pod, and which ones are ports that the user added while no explicit exposure is defined in the pod (so he's on his own, if there's nothing listening on them he'll have users face non-functional or no reposonses at all).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23463) Properties: Build pod has state of exit code 0 instead of correct status completed
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23463?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23463:
-------------------------------------
Description:
When I create a new OpenShift 3 application from a template, there is a running build. Once a build pod is completed, it has status "Completed". But now it Pods tabbed properties it contains status "Exit Code: 0" which is not user friendly and it broke integration tests.
steps:
# EXEC: create an application via a s2i template
# EXEC: in OpenShift explorer: select the connection that you used to create the application and open up the "Properties view"
# EXEC: in Properties: select "Pods" tab.
# ASSERT: a build pod is appearing
# EXEC: wait until the build pod is terminated and then look at its "Status" in the Properties > Pods
Result:
The status for the pod is reported with a "Exit Code: 0" (if successfully terminated, "Exit Code: 1" otherwise)
!exit-code-0.png!
was:
When I create a new OpenShift 3 application from a template, there is a running build. Once a build pod is completed, it has status "Completed". But now it Pods tabbed properties it contains status "Exit Code: 0" which is not user friendly and it broke integration tests.
steps:
# EXEC: create an application via a s2i template
# EXEC: in OpenShift explorer: select the connection that you used to create the application and open up the "Properties view"
# EXEC: in Properties: select "Pods" tab.
# ASSERT: a build pod is appearing
# EXEC: wait until the build is finished, the build pod is terminated and then look at its "Status" in the Properties > Pods
Result:
The status for the pod is reported with a "Exit Code: 0" (if successfully terminated, "Exit Code: 1" otherwise)
!exit-code-0.png!
> Properties: Build pod has state of exit code 0 instead of correct status completed
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-23463
> URL: https://issues.jboss.org/browse/JBIDE-23463
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Marián Labuda
> Priority: Minor
> Labels: openshift_v3
> Fix For: 4.4.x
>
> Attachments: exit-code-0.png
>
>
> When I create a new OpenShift 3 application from a template, there is a running build. Once a build pod is completed, it has status "Completed". But now it Pods tabbed properties it contains status "Exit Code: 0" which is not user friendly and it broke integration tests.
> steps:
> # EXEC: create an application via a s2i template
> # EXEC: in OpenShift explorer: select the connection that you used to create the application and open up the "Properties view"
> # EXEC: in Properties: select "Pods" tab.
> # ASSERT: a build pod is appearing
> # EXEC: wait until the build pod is terminated and then look at its "Status" in the Properties > Pods
> Result:
> The status for the pod is reported with a "Exit Code: 0" (if successfully terminated, "Exit Code: 1" otherwise)
> !exit-code-0.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23463) Properties: Build pod has state of exit code 0 instead of correct status completed
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23463?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23463:
-------------------------------------
Description:
When I create a new OpenShift 3 application from a template, there is a running build. Once a build pod is completed, it has status "Completed". But now it Pods tabbed properties it contains status "Exit Code: 0" which is not user friendly and it broke integration tests.
steps:
# EXEC: create an application via a s2i template
# EXEC: in OpenShift explorer: select the connection that you used to create the application and open up the "Properties view"
# EXEC: in Properties: select "Pods" tab.
# ASSERT: a build pod is appearing
# EXEC: wait until the build is finished, the build pod is terminated and then look at its "Status" in the Properties > Pods
Result:
The status for the pod is reported with a "Exit Code: 0" (if successfully terminated, "Exit Code: 1" otherwise)
!exit-code-0.png!
was:
When I create a new OpenShift 3 application from a template, there is a running build. Once a build pod is completed, it has status "Completed". But now it Pods tabbed properties it contains status "Exit Code: 0" which is not user friendly and it broke integration tests.
steps:
# EXEC: create an application via a s2i template
# ASSERT: in Properties: a build pod is appearing
# EXEC: wait until the build is finished, the build pod is terminated and then look at its "Status" in the Properties > Pods
Result:
The status for the pod is reported with a "Exit Code: 0" (if successfully terminated, "Exit Code: 1" otherwise)
!exit-code-0.png!
> Properties: Build pod has state of exit code 0 instead of correct status completed
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-23463
> URL: https://issues.jboss.org/browse/JBIDE-23463
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Marián Labuda
> Priority: Minor
> Labels: openshift_v3
> Fix For: 4.4.x
>
> Attachments: exit-code-0.png
>
>
> When I create a new OpenShift 3 application from a template, there is a running build. Once a build pod is completed, it has status "Completed". But now it Pods tabbed properties it contains status "Exit Code: 0" which is not user friendly and it broke integration tests.
> steps:
> # EXEC: create an application via a s2i template
> # EXEC: in OpenShift explorer: select the connection that you used to create the application and open up the "Properties view"
> # EXEC: in Properties: select "Pods" tab.
> # ASSERT: a build pod is appearing
> # EXEC: wait until the build is finished, the build pod is terminated and then look at its "Status" in the Properties > Pods
> Result:
> The status for the pod is reported with a "Exit Code: 0" (if successfully terminated, "Exit Code: 1" otherwise)
> !exit-code-0.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months