March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21913) Server Adapter wizard: route is not changed when I select a different service

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21913?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21913: ------------------------------------- Fix Version/s: 4.3.1.CR1 > Server Adapter wizard: route is not changed when I select a different service > ----------------------------------------------------------------------------- > > Key: JBIDE-21913 > URL: https://issues.jboss.org/browse/JBIDE-21913 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.1.CR1 > > > # ASSERT: have a project with at least 2 services and 2 routes (ex. nodejs-example and eap-app services) > # EXEC: launch OpenShift 3 Server Adapter wizard > # ASSERT: eap-app service is selected > # ASSERT: accordingly *eap-app* route is selected in "Use Route:" > # EXEC: select eap-app service > Result: > "Use Route" is still set to *eap-app* route > Expected result: > "Use Route" should be set to *nodejs-example* route -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21913) Server Adapter wizard: route is not changed when I select a different service

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21913?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-21913: ---------------------------------------- Assignee: Andre Dietisheim > Server Adapter wizard: route is not changed when I select a different service > ----------------------------------------------------------------------------- > > Key: JBIDE-21913 > URL: https://issues.jboss.org/browse/JBIDE-21913 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.1.CR1 > > > # ASSERT: have a project with at least 2 services and 2 routes (ex. nodejs-example and eap-app services) > # EXEC: launch OpenShift 3 Server Adapter wizard > # ASSERT: eap-app service is selected > # ASSERT: accordingly *eap-app* route is selected in "Use Route:" > # EXEC: select eap-app service > Result: > "Use Route" is still set to *eap-app* route > Expected result: > "Use Route" should be set to *nodejs-example* route -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21913) Server Adapter wizard: route is not changed when I select a different service

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21913?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21913: ------------------------------------- Description: # ASSERT: have a project with at least 2 services and 2 routes (ex. nodejs-example and eap-app services) # EXEC: launch OpenShift 3 Server Adapter wizard # ASSERT: eap-app service is selected # ASSERT: accordingly *eap-app* route is selected in "Use Route:" # EXEC: select eap-app service Result: "Use Route" is still set to *eap-app* route Expected result: "Use Route" should be set to *nodejs-example* route > Server Adapter wizard: route is not changed when I select a different service > ----------------------------------------------------------------------------- > > Key: JBIDE-21913 > URL: https://issues.jboss.org/browse/JBIDE-21913 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Andre Dietisheim > > # ASSERT: have a project with at least 2 services and 2 routes (ex. nodejs-example and eap-app services) > # EXEC: launch OpenShift 3 Server Adapter wizard > # ASSERT: eap-app service is selected > # ASSERT: accordingly *eap-app* route is selected in "Use Route:" > # EXEC: select eap-app service > Result: > "Use Route" is still set to *eap-app* route > Expected result: > "Use Route" should be set to *nodejs-example* route -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21913) Server Adapter wizard: route is not changed when I select a different service

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-21913: ---------------------------------------- Summary: Server Adapter wizard: route is not changed when I select a different service Key: JBIDE-21913 URL: https://issues.jboss.org/browse/JBIDE-21913 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Andre Dietisheim -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21904) Pod deployment path is not reflecting selected service

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21904?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21904: ------------------------------------- Description: Having more services under an OpenShift 3 connection and trying to create a new OS 3 server adapter does not use correct pod deployment path in following scenario: I am having a project with eap application (created from eap 64 basic s2i) and nodejs application. When I select nodejs application /opt/apt-root/src is used as a Pod Deployment Path. After selecting an EAP service, Pod Deployment Path is changed to /opt/eap/standalone/deployments. When I select nodejs in this point, Pod Deployment Path is not updated again and value is still /opt/eap/standalone/deployments, what is wrong. # ASSERT: have a project with 2 services (eap-app, nodejs-example) # EXEC: launch new OpenShift 3 Server Adapter wizard # EXEC: select nodejs-example service # ASSERT: "Pod Deployment Path" is set to */opt/apt-root/src* # EXEC: select eap-app service # ASSERT: "Pod Deployment Path" is set to */opt/eap/standalone/deployments* # EXEC: select nodejs-example service Result: "Pod Deployment Path" is still */opt/apt-root/src* Expected Result: "Pod Deployment Path" should be set to */opt/eap/standalone/deployments* was: Having more services under an OpenShift 3 connection and trying to create a new OS 3 server adapter does not use correct pod deployment path in following scenario: I am having a project with eap application (created from eap 64 basic s2i) and nodejs application. When I select nodejs application /opt/apt-root/src is used as a Pod Deployment Path. After selecting an EAP service, Pod Deployment Path is changed to /opt/eap/standalone/deployments. When I select nodejs in this point, Pod Deployment Path is not updated again and value is still /opt/eap/standalone/deployments, what is wrong. > Pod deployment path is not reflecting selected service > ------------------------------------------------------ > > Key: JBIDE-21904 > URL: https://issues.jboss.org/browse/JBIDE-21904 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Fix For: 4.3.1.CR1 > > > Having more services under an OpenShift 3 connection and trying to create a new OS 3 server adapter does not use correct pod deployment path in following scenario: > I am having a project with eap application (created from eap 64 basic s2i) and nodejs application. When I select nodejs application /opt/apt-root/src is used as a Pod Deployment Path. After selecting an EAP service, Pod Deployment Path is changed to /opt/eap/standalone/deployments. When I select nodejs in this point, Pod Deployment Path is not updated again and value is still /opt/eap/standalone/deployments, what is wrong. > # ASSERT: have a project with 2 services (eap-app, nodejs-example) > # EXEC: launch new OpenShift 3 Server Adapter wizard > # EXEC: select nodejs-example service > # ASSERT: "Pod Deployment Path" is set to */opt/apt-root/src* > # EXEC: select eap-app service > # ASSERT: "Pod Deployment Path" is set to */opt/eap/standalone/deployments* > # EXEC: select nodejs-example service > Result: > "Pod Deployment Path" is still */opt/apt-root/src* > Expected Result: > "Pod Deployment Path" should be set to */opt/eap/standalone/deployments* -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21857: ------------------------------------- I tried Oracle JDK 1.6.something and 1.8.something, same problems > Hot class reload doesn't work on OpenShift > ------------------------------------------ > > Key: JBIDE-21857 > URL: https://issues.jboss.org/browse/JBIDE-21857 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Thomas Mäder > Priority: Blocker > Fix For: 4.3.1.CR1 > > > When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will : > - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync > - will always fail if a method signature changed, the debugger saying JDK is out of sync > Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server) > This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21857: --------------------------------------------- Anyone who can reproduce this on Oracle JDK ? > Hot class reload doesn't work on OpenShift > ------------------------------------------ > > Key: JBIDE-21857 > URL: https://issues.jboss.org/browse/JBIDE-21857 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Thomas Mäder > Priority: Blocker > Fix For: 4.3.1.CR1 > > > When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will : > - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync > - will always fail if a method signature changed, the debugger saying JDK is out of sync > Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server) > This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21904) Pod deployment path is not reflecting selected service

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21904?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21904: ------------------------------------------ [~scabanovich] yes I agree, this is thightly related to JBIDE-21830 and JBIDE-21858. I'll include the fixes for this and the other issues in a single PR. > Pod deployment path is not reflecting selected service > ------------------------------------------------------ > > Key: JBIDE-21904 > URL: https://issues.jboss.org/browse/JBIDE-21904 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Fix For: 4.3.1.CR1 > > > Having more services under an OpenShift 3 connection and trying to create a new OS 3 server adapter does not use correct pod deployment path in following scenario: > I am having a project with eap application (created from eap 64 basic s2i) and nodejs application. When I select nodejs application /opt/apt-root/src is used as a Pod Deployment Path. After selecting an EAP service, Pod Deployment Path is changed to /opt/eap/standalone/deployments. When I select nodejs in this point, Pod Deployment Path is not updated again and value is still /opt/eap/standalone/deployments, what is wrong. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3664) Do we still need/want custom build of vagrant ?

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3664?page=com.atlassian.jira.plugin.... ] Jan Richter commented on JBDS-3664: ----------------------------------- [~dgolovin], try passing in VAGRANTAPPDIR='blablabla' instead of INSTALLDIR. > Do we still need/want custom build of vagrant ? > ----------------------------------------------- > > Key: JBDS-3664 > URL: https://issues.jboss.org/browse/JBDS-3664 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > > we seem to install use our custom vagrant build. > Is that still relevant ? > With that we need to test much more since our build could be different. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21904) Pod deployment path is not reflecting selected service

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21904?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21904: ----------------------------------- Assignee: Andre Dietisheim (was: Fred Bricon) > Pod deployment path is not reflecting selected service > ------------------------------------------------------ > > Key: JBIDE-21904 > URL: https://issues.jboss.org/browse/JBIDE-21904 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Fix For: 4.3.1.CR1 > > > Having more services under an OpenShift 3 connection and trying to create a new OS 3 server adapter does not use correct pod deployment path in following scenario: > I am having a project with eap application (created from eap 64 basic s2i) and nodejs application. When I select nodejs application /opt/apt-root/src is used as a Pod Deployment Path. After selecting an EAP service, Pod Deployment Path is changed to /opt/eap/standalone/deployments. When I select nodejs in this point, Pod Deployment Path is not updated again and value is still /opt/eap/standalone/deployments, what is wrong. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 March 2016