October 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24646) Import application: doesnt check if local branch match

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-24646?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24646: ------------------------------- Sprint: devex #156 October 2018, devex #157 November 2019 (was: devex #156 October 2018) > Import application: doesnt check if local branch match > ------------------------------------------------------ > > Key: JBIDE-24646 > URL: https://issues.jboss.org/browse/JBIDE-24646 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Jan Novak > Assignee: Dmitrii Bocharov > Priority: Major > Labels: import_app, openshift_v3 > Fix For: 4.10.0.AM1 > > > Importing project from Openshift > * use existing repo > * local repo uses different branch than Openshift > * remote branch isnt locally fetched > * import finishes succesfully > * in local repo is *stil checkouted wrong branch*, without any warnings -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26330) Server adapter: shutting down Eclipse won't reset the maven profile that the adapter activated in the project

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26330?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26330: ------------------------------- Sprint: devex #156 October 2018, devex #157 November 2019 (was: devex #156 October 2018) > Server adapter: shutting down Eclipse won't reset the maven profile that the adapter activated in the project > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26330 > URL: https://issues.jboss.org/browse/JBIDE-26330 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.9.0.AM2 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Priority: Major > Fix For: 4.10.0.AM1 > > > steps: > # EXEC: create the "hello" application in OpenShift as outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... > # EXEC: import the "hello" maven project into your Eclipse > # EXEC: create a server adapter and start it > # ASSERT: server adapter for project "hello" is *[Started, Synchronized]* > # EXEC: in the Project Explorer: pick Maven > Select Maven Profiles... > # ASSERT: *"openshift"* maven profile is selected > # EXEC: Restart Eclipse > # ASSERT: server adapter for project "hello" is *[Stopped, Republish]* > # EXEC: in the Project Explorer: pick Maven > Select Maven Profiles... > Result: > Project "hello" still has *"openshift"* profile selected > Expected result: > Project "hello" still has *no profile* selected (starting the server adapter selects the "openshift" profile, while stopping it unselects it.) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[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, devex #156 October 2018, devex #157 November 2019 (was: devex #154 September 2018, devex #155 September 2018, devex #156 October 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 > Priority: Major > Labels: server_adapter > Fix For: 4.10.0.AM1 > > > 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. Debugging doesn't work any more because the port forwarding was stopped. To have it running again you need to restart the port forwarding for the new pod. > 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.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25000) Server adapter: starting into debugging fails initially (succeeds on a latter try)

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25000: ------------------------------- Sprint: devex #138 September 2017, devex #152 July 2018, devex #153 August 2018, devex #154 September 2018, devex #155 September 2018, devex #156 October 2018, devex #157 November 2019 (was: devex #138 September 2017, devex #152 July 2018, devex #153 August 2018, devex #154 September 2018, devex #155 September 2018, devex #156 October 2018) > Server adapter: starting into debugging fails initially (succeeds on a latter try) > ---------------------------------------------------------------------------------- > > Key: JBIDE-25000 > URL: https://issues.jboss.org/browse/JBIDE-25000 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Major > Labels: openshift_v3, server_adapter > Fix For: 4.10.0.AM1 > > Attachments: failed-to-connect-v8-vm.png > > > # ASSERT: have an application running in *[OpenShift Online|https://console.starter-us-east-2.openshift.com/]* based on the "nodejs-mongo-persistent" template > # ASSERT: have a server adapter for it > # EXEC/ASSERT: have the adapter started in non-debugging/normal mode > # EXEC: restart the adapter debugging > Result: > !failed-to-connect-v8-vm.png! > {code} > java.io.IOException: Failed to get version > at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79) > at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207) > at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74) > at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039) > at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.util.concurrent.FutureTask.get(FutureTask.java:206) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127) > ... 9 more > Caused by: java.io.IOException: End of stream > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127) > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104) > at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158) > {code} > ps. this can be simulated in the CDK, by having everything set and once the pod is up and ithe adapter is in debug, stopping the port forwarding. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26255) Cannot OpenOn existing xhtml web page in faces-config.xml

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26255?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26255: ------------------------------- Sprint: devex #154 September 2018, devex #155 September 2018, devex #156 October 2018, devex #157 November 2019 (was: devex #154 September 2018, devex #155 September 2018, devex #156 October 2018) > Cannot OpenOn existing xhtml web page in faces-config.xml > --------------------------------------------------------- > > Key: JBIDE-26255 > URL: https://issues.jboss.org/browse/JBIDE-26255 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.9.0.AM1 > Reporter: Ondrej Dockal > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.10.0.AM1 > > Attachments: openon-faces-config.gif > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26158) [UPSTREAM] Server adapter: NPE when starting adapter for nodejs-mongo-persistent into Debug

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26158?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26158: ------------------------------- Sprint: devex #156 October 2018, devex #157 November 2019 (was: devex #156 October 2018) > [UPSTREAM] Server adapter: NPE when starting adapter for nodejs-mongo-persistent into Debug > -------------------------------------------------------------------------------------------- > > Key: JBIDE-26158 > URL: https://issues.jboss.org/browse/JBIDE-26158 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Major > Labels: upstream > Fix For: 4.10.x > > Attachments: image-2018-07-02-22-33-13-396.png, image-2018-07-02-22-49-45-246.png, image-2018-07-02-23-17-34-099.png, image-2018-07-03-00-03-56-346.png, screenshot-1.png, screenshot-2.png > > > steps: > # EXEC: launch new application wizard, choose nodejs-mongo-persistent template and finish > # EXEC: when asked import the app and create a server adapter > # ASSERT: server adapter is created > # EXEC: start the server adapter > # ASSERT: server adapter is launched > # EXEC: restart the server adapter into Debug > Result: > Debuggin works, but you get the following error dialog: > !image-2018-07-02-22-33-13-396.png! > In the Eclipse log you'll find the following: > {code} > java.lang.NullPointerException > at org.eclipse.core.internal.resources.CheckMissingNaturesListener.updateRange(CheckMissingNaturesListener.java:209) > at org.eclipse.core.internal.resources.CheckMissingNaturesListener$3.runInWorkspace(CheckMissingNaturesListener.java:179) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60) > {code} > ps. project context menu: Convert > Javascript Project doesn't help. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23725) Automate test JBDS-5892 Bean discovery in explicit and implicit archives is supported (CDI1.1+)

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-23725?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23725: ------------------------------- Sprint: devex #155 September 2018, devex #156 October 2018, devex #157 November 2019 (was: devex #155 September 2018, devex #156 October 2018) > Automate test JBDS-5892 Bean discovery in explicit and implicit archives is supported (CDI1.1+) > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23725 > URL: https://issues.jboss.org/browse/JBIDE-23725 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdi, integration-tests > Reporter: Lukáš Valach > Assignee: Ondrej Dockal > Priority: Minor > Fix For: 4.10.0.AM1 > > > Automate test JBDS-5892 Bean discovery in explicit and implicit archives is supported (CDI1.1+) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24442) Import wizard: does nothing if server is not reachable

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-24442?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24442: ------------------------------- Sprint: devex #156 October 2018, devex #157 November 2019 (was: devex #156 October 2018) > Import wizard: does nothing if server is not reachable > ------------------------------------------------------ > > Key: JBIDE-24442 > URL: https://issues.jboss.org/browse/JBIDE-24442 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Priority: Major > Fix For: 4.10.0.AM1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26443) Openshift Itests: update OC in ITests suites

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26443?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26443: ---------------------------------- Story Points: 3 > Openshift Itests: update OC in ITests suites > -------------------------------------------- > > Key: JBIDE-26443 > URL: https://issues.jboss.org/browse/JBIDE-26443 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Affects Versions: 4.10.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.10.0.AM1 > > > In ITests is used oc version 3.9, update to 3.11, which is not available. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26444) Integration Tests: Remove server dependencies from central ITests

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26444?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26444: ---------------------------------- Story Points: 3 > Integration Tests: Remove server dependencies from central ITests > ----------------------------------------------------------------- > > Key: JBIDE-26444 > URL: https://issues.jboss.org/browse/JBIDE-26444 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central, integration-tests > Affects Versions: 4.10.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.10.0.AM1 > > > Server dependencies could be removed and central itests should be refactored accordingly. > I suppose there is no need to deploy all quickstarts on server. > [~psrna] can you please confirm? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2018