August 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26180) TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26180?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26180: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.9.x* > TP: create target platform based on Eclipse 4.9 (Simrel 2018-09) > ---------------------------------------------------------------- > > Key: JBIDE-26180 > URL: https://issues.jboss.org/browse/JBIDE-26180 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.9.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.9.0.AM1, 4.9.0.AM3, 4.9.0.Final, 4.9.x > > Attachments: am1-vs-am2.p2diff.txt > > > In order to start Eclipse 4.9-based builds, we need an updated target platform. > For sprint 152 / AM1: simrel M1 > For sprint 153 / AM2: simrel M2 > For sprint 154 / AM3: simrel M3 > For sprint 155 / GA: simrel RC2/GA > Coming in the next update, some orbit changes: > * batik, icu4j, platform, felix gogo, httpclient (due 27 Aug) > Also: > * reddeer 2.3 > * m2e http://download.eclipse.org/technology/m2e/milestones/1.9/1.9.1.20180821-... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26165) Implement a Launcher project wizard

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26165?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26165: ------------------------------- Fix Version/s: 4.9.x (was: 4.9.0.AM2) > Implement a Launcher project wizard > ----------------------------------- > > Key: JBIDE-26165 > URL: https://issues.jboss.org/browse/JBIDE-26165 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.6.0.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Fix For: 4.9.x > > > Implements a Launcher based project wizard using the implemented model -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26165) Implement a Launcher project wizard

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26165?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26165: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.9.x* > Implement a Launcher project wizard > ----------------------------------- > > Key: JBIDE-26165 > URL: https://issues.jboss.org/browse/JBIDE-26165 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.6.0.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Fix For: 4.9.x > > > Implements a Launcher based project wizard using the implemented model -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26160) Server Adapter: erroneously stays in [Debugging] when you kill the pod

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26160?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26160: ------------------------------- Fix Version/s: 4.9.x (was: 4.9.0.AM2) > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26160) Server Adapter: erroneously stays in [Debugging] when you kill the pod

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26160?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26160: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.9.x* > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26159) Server adapter: debugging is not stopped if you delete the pod

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26159?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26159: ------------------------------- Fix Version/s: 4.9.x (was: 4.9.0.AM2) > Server adapter: debugging is not stopped if you delete the pod > -------------------------------------------------------------- > > Key: JBIDE-26159 > URL: https://issues.jboss.org/browse/JBIDE-26159 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Priority: Minor > Labels: port_forwarding, server_adapter > Fix For: 4.9.x > > > steps: > Screencast: https://youtu.be/XMA--S9zj6s > # EXEC: create an application (via ex. nodejs-mongo-persistent template) > # ASSERT: pod for service is running > # EXEC: select pod and pick "Port Forwarding..." and start the forwarding > # ASSERT: forwarding is running > # EXEC: verify on the cmd-line that the forwarding is running > {code} > $ ps ax | grep oc > 47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080 > {code} > # EXEC: in Explorer: select the pod for your service and pick "Delete" > # ASSERT: pod gets deleted and recreated > # EXEC: verify on the cmd-line that the forwarding is running > {code} > $ ps ax | grep oc > 47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080 > {code} > Result: > The port forwarding is still running. > In Eclipse there's no way for you to see this since you have to select the new pod and pick "Port Forwarding..." on this new pod. It'll then tell you that the port forwarding is *NOT* running, since we're asking about port-forwarding for the new pod (not the old one that was killed). > PS. it looks like there's a timeout somewhere, oc stops port-forwarding at some point (many minutes later) and the process disappears. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26159) Server adapter: debugging is not stopped if you delete the pod

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26159?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26159: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.9.x* > Server adapter: debugging is not stopped if you delete the pod > -------------------------------------------------------------- > > Key: JBIDE-26159 > URL: https://issues.jboss.org/browse/JBIDE-26159 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Priority: Minor > Labels: port_forwarding, server_adapter > Fix For: 4.9.x > > > steps: > Screencast: https://youtu.be/XMA--S9zj6s > # EXEC: create an application (via ex. nodejs-mongo-persistent template) > # ASSERT: pod for service is running > # EXEC: select pod and pick "Port Forwarding..." and start the forwarding > # ASSERT: forwarding is running > # EXEC: verify on the cmd-line that the forwarding is running > {code} > $ ps ax | grep oc > 47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080 > {code} > # EXEC: in Explorer: select the pod for your service and pick "Delete" > # ASSERT: pod gets deleted and recreated > # EXEC: verify on the cmd-line that the forwarding is running > {code} > $ ps ax | grep oc > 47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080 > {code} > Result: > The port forwarding is still running. > In Eclipse there's no way for you to see this since you have to select the new pod and pick "Port Forwarding..." on this new pod. It'll then tell you that the port forwarding is *NOT* running, since we're asking about port-forwarding for the new pod (not the old one that was killed). > PS. it looks like there's a timeout somewhere, oc stops port-forwarding at some point (many minutes later) and the process disappears. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26231) Implement state persistence

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26231?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26231: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.9.x* > Implement state persistence > --------------------------- > > Key: JBIDE-26231 > URL: https://issues.jboss.org/browse/JBIDE-26231 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-server-protocol > Affects Versions: 4.9.0.AM1 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Fix For: 4.9.x > > > Server definitions and search pathes should be persistent so that users don't loose their work -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26230) Implement Tycho build

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26230?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26230: ------------------------------- Fix Version/s: 4.9.x (was: 4.9.0.AM2) > Implement Tycho build > --------------------- > > Key: JBIDE-26230 > URL: https://issues.jboss.org/browse/JBIDE-26230 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-server-protocol > Affects Versions: 4.9.0.AM1 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Fix For: 4.9.x > > > Switch the Maven build to Tycho for: > * centralized management of dependencies > * unit tests in OSGI env -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26230) Implement Tycho build

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26230?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26230: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.9.x* > Implement Tycho build > --------------------- > > Key: JBIDE-26230 > URL: https://issues.jboss.org/browse/JBIDE-26230 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-server-protocol > Affects Versions: 4.9.0.AM1 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Fix For: 4.9.x > > > Switch the Maven build to Tycho for: > * centralized management of dependencies > * unit tests in OSGI env -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 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 August 2018