June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22648) RSE launches stick around in debug view forever

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22648?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-22648. --------------------------------- Resolution: Done Pushed to master > RSE launches stick around in debug view forever > ----------------------------------------------- > > Key: JBIDE-22648 > URL: https://issues.jboss.org/browse/JBIDE-22648 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.4.1.M1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.1.M1 > > > When launching remote rse wildfly / eap / etc, launches get stuck and left behind, never cleaned up. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22648) RSE launches stick around in debug view forever

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22648?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22648: -------------------------------- Story Points: 7.5 (was: 6) > RSE launches stick around in debug view forever > ----------------------------------------------- > > Key: JBIDE-22648 > URL: https://issues.jboss.org/browse/JBIDE-22648 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.4.1.M1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.1.M1 > > > When launching remote rse wildfly / eap / etc, launches get stuck and left behind, never cleaned up. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22648) RSE launches stick around in debug view forever

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22648?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22648: ------------------------------------- Manual test cases: Prereq: Create an RSE connection to a remote host, rse+fs or rse+mgmt (or test both... ugh, so many to do) Test: Perform actions required below, and make sure debug view is properly cleaned up or represented with launches. In general, you will want a launch to be visible while the server is up, and disappear when you stop the server. The launch should have 1 "process" attached to it, and may or may not include a debugging connection, depending on settings Scenarios: 1) Run Mode a) Start server in run mode, b) right-click on the process in debug view and select "Properties". Verify a command is visible c) then stop server 2) Debug Mode a) Start server in Debug mode, b) right-click on the process in debug view and select "Properties". Verify a command is visible. c) Copy this command to clipboard, you will use it later when we switch to externally launched d) then stop server 3) Open server editor and mark server as externally managed, save the changes 4) Switch to your terminal, and start the DEBUG command you copied from 2b) on the remote system. 5) Externally-managed Run Mode a) Start server in run mode, b) right-click on the process in debug view and select "Properties". Verify command is NOT VISIBLE / IS EMPTY c) then stop server 6) Externally-managed Debug Mode a) Start server in Debug mode, b) Verify a launch is visible, with a process AND a debug connection! b) right-click on the process in debug view and select "Properties". Verify command is NOT VISIBLE / IS EMPTY c) then stop server TERMINATION TESTS 7) Externally-managed Run Mode Termination a) Start server in run mode, b) right-click on the PROCESS (not debugger) in debug view and verify you CANNOT terminate the process c) then stop server 8) Externally-managed Debug Mode Termination a) Start server in Debug mode, b) right-click on the PROCESS (not debugger) in debug view and verify you CANNOT terminate the process c) then stop server 9) Open server editor and mark server as NOT externally managed, save the changes 10) Switch to your terminal, and KILL the process or shut down the server 11) Run Mode a) Start server in run mode, b) right-click on the process in debug view and select "terminate". Verify the server properly shuts down and all processes are cleaned up in debug view c) then stop server 12) Debug Mode a) Start server in Debug mode, b) right-click on the process in debug view and select "terminate". Verify the server properly shuts down and all processes are cleaned up in debug view c) then stop server Switch to RSE+MGMT and perform all 12 again ;) If you see a usecase which doesn't work as outlined above, OR if you see a usecase which *does* function as above but you think it shouldn't, tell me and we can discuss it! :D > RSE launches stick around in debug view forever > ----------------------------------------------- > > Key: JBIDE-22648 > URL: https://issues.jboss.org/browse/JBIDE-22648 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.4.1.M1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.1.M1 > > > When launching remote rse wildfly / eap / etc, launches get stuck and left behind, never cleaned up. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22570) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Central]

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22570?page=com.atlassian.jira.plugi... ] Fred Bricon closed JBIDE-22570. ------------------------------- > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Central] > ---------------------------------------------------------- > > Key: JBIDE-22570 > URL: https://issues.jboss.org/browse/JBIDE-22570 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central, maven, project-examples > Affects Versions: 4.4.1.M1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Blocker > Labels: task > Fix For: 4.4.1.M1 > > > For JBIDE 4.4.1.Alpha1 [Central]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22559) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Hibernate]

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22559?page=com.atlassian.jira.plugi... ] Fred Bricon closed JBIDE-22559. ------------------------------- Resolution: Done Commits were committed > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Hibernate] > ------------------------------------------------------------ > > Key: JBIDE-22559 > URL: https://issues.jboss.org/browse/JBIDE-22559 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Blocker > Labels: task > Fix For: 4.4.1.M1 > > > For JBIDE 4.4.1.Alpha1 [Hibernate]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Hibernate task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22570) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Central]

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22570?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-22570. --------------------------------- Resolution: Done Version fixed. Blue balls are blue > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Central] > ---------------------------------------------------------- > > Key: JBIDE-22570 > URL: https://issues.jboss.org/browse/JBIDE-22570 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central, maven, project-examples > Affects Versions: 4.4.1.M1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Blocker > Labels: task > Fix For: 4.4.1.M1 > > > For JBIDE 4.4.1.Alpha1 [Central]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22653) Can't scale pods down to 0

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22653?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22653: ------------------------------------ You can theoretically reach 0 pod using JBossTools: if you have 1 pod and select Scale down or scale to 0, then user will not get a refusal, action is executed but it does nothing and user will not get any notification > Can't scale pods down to 0 > -------------------------- > > Key: JBIDE-22653 > URL: https://issues.jboss.org/browse/JBIDE-22653 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Fred Bricon > > The scale to... menu lets you scale to any number of replicas, but you can't go down to 0. > The webconsoles allows it, albeit with a big warning: "Are you sure you want to scale deploymentname to 0 replicas? This will stop all pods for the deployment." > My take is we should have the same behavior in eclipse -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22241) OpenShift Explorer: Cascade resource deletion

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22241?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22241: -------------------------------- Sprint: (was: devex #116 June 2016) > OpenShift Explorer: Cascade resource deletion > --------------------------------------------- > > Key: JBIDE-22241 > URL: https://issues.jboss.org/browse/JBIDE-22241 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: explorer, openshift_v3, ux > Fix For: 4.4.1.M1 > > > It would be nice to have a possibility to allow cascading deletion, deletion of related resource/resource managed by the resource which is about to be deleted. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22241) OpenShift Explorer: Cascade resource deletion

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22241?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22241: -------------------------------- Sprint: devex #117 July 2016 > OpenShift Explorer: Cascade resource deletion > --------------------------------------------- > > Key: JBIDE-22241 > URL: https://issues.jboss.org/browse/JBIDE-22241 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: explorer, openshift_v3, ux > Fix For: 4.4.1.M1 > > > It would be nice to have a possibility to allow cascading deletion, deletion of related resource/resource managed by the resource which is about to be deleted. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22653) Can't scale pods down to 0

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-22653: ----------------------------------- Summary: Can't scale pods down to 0 Key: JBIDE-22653 URL: https://issues.jboss.org/browse/JBIDE-22653 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.4.0.Final Reporter: Fred Bricon The scale to... menu lets you scale to any number of replicas, but you can't go down to 0. The webconsoles allows it, albeit with a big warning: "Are you sure you want to scale deploymentname to 0 replicas? This will stop all pods for the deployment." My take is we should have the same behavior in eclipse -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 June 2016