[JBoss JIRA] (JBIDE-26160) Server Adapter: erroneously stays in [Debugging] when you kill the pod
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26160?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26160:
-------------------------------
Sprint: devex #154 September 2018, devex #155 September 2018 (was: devex #154 September 2018)
> Server Adapter: erroneously stays in [Debugging] when you kill the pod
> ----------------------------------------------------------------------
>
> Key: JBIDE-26160
> URL: https://issues.jboss.org/browse/JBIDE-26160
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Labels: server_adapter
> Fix For: 4.9.x
>
>
> steps:
> # EXEC: create an application (via ex. nodejs-mongo-persistent template), import the project and create a server adapter for it
> # ASSERT: server adapter is created
> # EXEC: start the server adapter in Debugging
> # ASSERT: sever adapter is in *[Debugging, Synchronized]* state
> # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is started
> # EXEC: in Explorer: select the pod for your service and pick "Delete"
> # ASSERT: pod gets deleted and recreated
> # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is stopped
> Result:
> The server adapter still says that is is *[Debugging, Synchronized]*, but debugging is not working any more. The new pod is not running in debug (dev-) mode any more. To have it running again you need to restart the server adapter into debug, which will re-create a new pod in debug-mode.
> Expected result:
> Server adapter should get out of debugging and back into normal run mode *[Started, Synchronized]*.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (ERT-647) Resolve remaining issues with Batik 1.9.1
by Sopot Cela (JIRA)
[ https://issues.jboss.org/browse/ERT-647?page=com.atlassian.jira.plugin.sy... ]
Sopot Cela updated ERT-647:
---------------------------
Sprint: devex #152 July 2018, devex #153 August 2018, devex #155 September 2018 (was: devex #152 July 2018, devex #153 August 2018, devex #154 September 2018)
> Resolve remaining issues with Batik 1.9.1
> -----------------------------------------
>
> Key: ERT-647
> URL: https://issues.jboss.org/browse/ERT-647
> Project: Eclipse Release Train
> Issue Type: Task
> Reporter: Roland Grunberg
> Assignee: Roland Grunberg
>
> Batik 1.9.1 had some remaining issues that prevented the full stack from being adopted during the Photon release train by some other projects (eg. Sirius, Papyrus, GMF, BIRT, Graphiti, etc.)
> We should resolve the remaining issues, re-include all the bundles in the stack and finally upgrade to Batik 1.10.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (ERT-656) Cannot run JUnit test method having parameter
by Sopot Cela (JIRA)
[ https://issues.jboss.org/browse/ERT-656?page=com.atlassian.jira.plugin.sy... ]
Sopot Cela updated ERT-656:
---------------------------
Sprint: devex #153 August 2018, devex #155 September 2018 (was: devex #153 August 2018, devex #154 September 2018)
> Cannot run JUnit test method having parameter
> ---------------------------------------------
>
> Key: ERT-656
> URL: https://issues.jboss.org/browse/ERT-656
> Project: Eclipse Release Train
> Issue Type: Task
> Affects Versions: Oxygen.1 (4.7), Photon (4.8), 2018-09 M2
> Reporter: Roland Grunberg
> Assignee: Roland Grunberg
>
> Since Oxygen.0, some changes introduced for JUnit 5 support, regressed the ability to run individual test methods that happen to take a parameter (eg. testFoo(TestContext) ). The filter matching against the method itself was broken.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months