September 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-24995) Server adapter: restarting into debug after restarting Eclipse errors

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24995?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24995: ------------------------------------- Description: reported originally in https://github.com/jbosstools/jbosstools-openshift/pull/1561#pullrequestr... (with slight different steps) # ASSERT: make sure that you have an app based on the "nodejs-mongo-persistent" template # ASSERT: make sure that you have the source imported to your workspace and a server adapter for it # EXEC: Server adapter: Start/Restart adapter Debugging # ASSERT: Server adapter: adapter is debugging, you see the debugging output in the console and the env vars have devmode set to true and the debugging port set to some value (5858 by default) # EXEC: Server adapter: Restart adapter (not debugging) Result: !image-2017-09-07-15-33-48-897.png! {code} com.openshift.restclient.OpenShiftException: Exception trying to PUT https://192.168.64.2:8443/oapi/v1/namespaces/nodejs/deploymentconfigs/nod... response code: 422 DeploymentConfig "nodejs-mongo-persistent" is invalid: spec.template.spec.containers[0].ports[2].name: Duplicate value: "debug" at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:114) at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:65) at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190) at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163) at okhttp3.RealCall.execute(RealCall.java:57) at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:258) at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:222) at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:210) at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:316) at org.jboss.tools.openshift.core.connection.Connection.updateResource(Connection.java:451) at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.sendAndGetNewPod(OpenShiftDebugMode.java:308) at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:220) at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController.launch(OpenShiftNodejsLaunchController.java:52) at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) 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.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566) at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502) at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) {code} was: # ASSERT: make sure that you have an app based on the "nodejs-mongo-persistent" template # ASSERT: make sure that you have the source imported to your workspace and a server adapter for it # EXEC: Server adapter: Start/Restart adapter Debugging # ASSERT: Server adapter: adapter is debugging, you see the debugging output in the console and the env vars have devmode set to true and the debugging port set to some value (5858 by default) # EXEC: Server adapter: Restart adapter (not debugging) Result: !image-2017-09-07-15-33-48-897.png! {code} com.openshift.restclient.OpenShiftException: Exception trying to PUT https://192.168.64.2:8443/oapi/v1/namespaces/nodejs/deploymentconfigs/nod... response code: 422 DeploymentConfig "nodejs-mongo-persistent" is invalid: spec.template.spec.containers[0].ports[2].name: Duplicate value: "debug" at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:114) at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:65) at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190) at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163) at okhttp3.RealCall.execute(RealCall.java:57) at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:258) at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:222) at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:210) at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:316) at org.jboss.tools.openshift.core.connection.Connection.updateResource(Connection.java:451) at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.sendAndGetNewPod(OpenShiftDebugMode.java:308) at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:220) at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController.launch(OpenShiftNodejsLaunchController.java:52) at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) 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.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566) at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502) at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) {code} > Server adapter: restarting into debug after restarting Eclipse errors > --------------------------------------------------------------------- > > Key: JBIDE-24995 > URL: https://issues.jboss.org/browse/JBIDE-24995 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.AM2 > Reporter: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.1.AM2 > > Attachments: image-2017-09-07-15-33-48-897.png > > > reported originally in https://github.com/jbosstools/jbosstools-openshift/pull/1561#pullrequestr... (with slight different steps) > # ASSERT: make sure that you have an app based on the "nodejs-mongo-persistent" template > # ASSERT: make sure that you have the source imported to your workspace and a server adapter for it > # EXEC: Server adapter: Start/Restart adapter Debugging > # ASSERT: Server adapter: adapter is debugging, you see the debugging output in the console and the env vars have devmode set to true and the debugging port set to some value (5858 by default) > # EXEC: Server adapter: Restart adapter (not debugging) > Result: > !image-2017-09-07-15-33-48-897.png! > {code} > com.openshift.restclient.OpenShiftException: Exception trying to PUT https://192.168.64.2:8443/oapi/v1/namespaces/nodejs/deploymentconfigs/nod... response code: 422 DeploymentConfig "nodejs-mongo-persistent" is invalid: spec.template.spec.containers[0].ports[2].name: Duplicate value: "debug" > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:114) > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:65) > at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190) > at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163) > at okhttp3.RealCall.execute(RealCall.java:57) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:258) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:222) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:210) > at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:316) > at org.jboss.tools.openshift.core.connection.Connection.updateResource(Connection.java:451) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.sendAndGetNewPod(OpenShiftDebugMode.java:308) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:220) > at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController.launch(OpenShiftNodejsLaunchController.java:52) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > 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.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4533) RPM should depend on upstream m2e-wtp rpms, including jaxrs, jpa, jsf

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4533?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4533: ---------------------------------- Pull latest version 1.3.3: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... --> http://download.jboss.org/jbosstools/updates/requirements/m2e-wtp/1.3.3.2... > RPM should depend on upstream m2e-wtp rpms, including jaxrs, jpa, jsf > --------------------------------------------------------------------- > > Key: JBDS-4533 > URL: https://issues.jboss.org/browse/JBDS-4533 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: 3rd-party-dependencies, rpm, target-platform, upstream > Affects Versions: 11.1.0.AM1 > Reporter: Nick Boldt > Fix For: 11.1.0.AM3 > > > RPM should depend on upstream m2e rpms, including jaxrs, jpa, jsf. Depends on getting this done in Fedora and devtools channel first. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4533) RPM should depend on upstream m2e-wtp rpms, including jaxrs, jpa, jsf

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4533?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4533: -------------------------------- Assignee: Nick Boldt > RPM should depend on upstream m2e-wtp rpms, including jaxrs, jpa, jsf > --------------------------------------------------------------------- > > Key: JBDS-4533 > URL: https://issues.jboss.org/browse/JBDS-4533 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: 3rd-party-dependencies, rpm, target-platform, upstream > Affects Versions: 11.1.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.1.0.AM3 > > > RPM should depend on upstream m2e rpms, including jaxrs, jpa, jsf. Depends on getting this done in Fedora and devtools channel first. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4533) RPM should depend on upstream m2e-wtp rpms, including jaxrs, jpa, jsf

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4533?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4533: ----------------------------- Fix Version/s: 11.1.0.AM3 (was: 11.x) > RPM should depend on upstream m2e-wtp rpms, including jaxrs, jpa, jsf > --------------------------------------------------------------------- > > Key: JBDS-4533 > URL: https://issues.jboss.org/browse/JBDS-4533 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: 3rd-party-dependencies, rpm, target-platform, upstream > Affects Versions: 11.1.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.1.0.AM3 > > > RPM should depend on upstream m2e rpms, including jaxrs, jpa, jsf. Depends on getting this done in Fedora and devtools channel first. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24939) update target platform & Central to Oxygen.1

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24939?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-24939 at 9/7/17 12:25 PM: -------------------------------------------------------------- Also, there's a new m2e-wtp build for Oxygen.1 at http://download.eclipse.org/m2e-wtp/milestones/oxygen/1.3/1.3.3.20170823-... was (Author: fbricon): Also, there's a new m2e-wtp build for Oxygen.1 at http://download.eclipse.org/m2e-wtp/milestones/oxygen/1.3/1.3.2.20170517-... > update target platform & Central to Oxygen.1 > -------------------------------------------- > > Key: JBIDE-24939 > URL: https://issues.jboss.org/browse/JBIDE-24939 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM2 > > > Issue to track changes to target platform after AM1. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24939) update target platform & Central to Oxygen.1

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24939?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-24939: ------------------------------------- Also, there's a new m2e-wtp build for Oxygen.1 at http://download.eclipse.org/m2e-wtp/milestones/oxygen/1.3/1.3.2.20170517-... > update target platform & Central to Oxygen.1 > -------------------------------------------- > > Key: JBIDE-24939 > URL: https://issues.jboss.org/browse/JBIDE-24939 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM2 > > > Issue to track changes to target platform after AM1. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24974) update TP to include org.sonatype.tycho.m2e 0.9.0 (currently 0.8.1)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24974?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24974: ------------------------------------ Reverted: https://github.com/jbosstools/jbosstools-target-platforms/commit/e09bf0ff... Building: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... >=11 > update TP to include org.sonatype.tycho.m2e 0.9.0 (currently 0.8.1) > ------------------------------------------------------------------- > > Key: JBIDE-24974 > URL: https://issues.jboss.org/browse/JBIDE-24974 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: maven, target-platform > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM2 > > > In Fedora, the latest org.sonatype.tycho.m2e 0.9.0, so we should use the same version in JBT/devstudio. > See: JBDS-4532 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24939) update target platform & Central to Oxygen.1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24939?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24939: ------------------------------------ Build's done. But [~aurelien.pupier] has reminded me that we can't move to m2e.tycho 0.9.0 (FUSETOOLS-2353, JBIDE-24974) so I'll have to revert that and respin. > update target platform & Central to Oxygen.1 > -------------------------------------------- > > Key: JBIDE-24939 > URL: https://issues.jboss.org/browse/JBIDE-24939 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM2 > > > Issue to track changes to target platform after AM1. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4532) RPM should depend on upstream m2e rpms, including apt, buildhelper, egit, mavenarchiver, maven importer, sourcelookup, & tycho

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4532?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-4532 at 9/7/17 12:10 PM: ----------------------------------------------------------- TODO: * update jbt/devstudio TP to use these newer versions: ** org.eclipse.m2e.feature, org.eclipse.m2e.tests.common, org.eclipse.m2e.importer 0.8.0 -> JBIDE-24973 --> latest: 1.8.1.20170728-1531 ** org.sonatype.tycho.m2e.feature 0.9.0 -> JBIDE-24974 --> latest: 0.9.0.201609252021 ** there's a problem with 0.9.0. Can we put 0.8.1 into Fedora instead of 0.9.0? See FUSETOOLS-2353 * build org.jboss.tools.maven.apt.feature 1.3.0 (or newer) in Koji -> BZ? * build org.jboss.tools.maven.sourcelookup.feature 1.8.101.v20170822-1709 (or newer) in Koji -> BZ? was (Author: nickboldt): TODO: * update jbt/devstudio TP to use these newer versions: ** org.eclipse.m2e.feature, org.eclipse.m2e.tests.common, org.eclipse.m2e.importer 0.8.0 -> JBIDE-24973 --> latest: 1.8.1.20170728-1531 ** org.sonatype.tycho.m2e.feature 0.9.0 -> JBIDE-24974 --> latest: 0.9.0.201609252021 * build org.jboss.tools.maven.apt.feature 1.3.0 (or newer) in Koji -> BZ? * build org.jboss.tools.maven.sourcelookup.feature 1.8.101.v20170822-1709 (or newer) in Koji -> BZ? > RPM should depend on upstream m2e rpms, including apt, buildhelper, egit, mavenarchiver, maven importer, sourcelookup, & tycho > ------------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-4532 > URL: https://issues.jboss.org/browse/JBDS-4532 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: 3rd-party-dependencies, rpm, target-platform, upstream > Affects Versions: 11.1.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.1.0.AM3 > > > RPM should depend on upstream m2e rpms, including apt, buildhelper, egit, mavenarchiver, maven importer, sourcelookup, & tycho. Depends on getting this done in Fedora and devtools channel first. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4532) RPM should depend on upstream m2e rpms, including apt, buildhelper, egit, mavenarchiver, maven importer, sourcelookup, & tycho

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4532?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4532: -------------------------------- Assignee: Nick Boldt > RPM should depend on upstream m2e rpms, including apt, buildhelper, egit, mavenarchiver, maven importer, sourcelookup, & tycho > ------------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-4532 > URL: https://issues.jboss.org/browse/JBDS-4532 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: 3rd-party-dependencies, rpm, target-platform, upstream > Affects Versions: 11.1.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.1.0.AM3 > > > RPM should depend on upstream m2e rpms, including apt, buildhelper, egit, mavenarchiver, maven importer, sourcelookup, & tycho. Depends on getting this done in Fedora and devtools channel first. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 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 September 2017