March 2016 - jbosstools-issues - Jboss List Archives

[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: Fred Bricon (was: Andre Dietisheim) > 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: Fred Bricon > 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] (JBIDE-21711) Server Adapter: Need a way to restart modules

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21711?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21711: ----------------------------------- Assignee: Rob Stryker (was: Andre Dietisheim) > Server Adapter: Need a way to restart modules > --------------------------------------------- > > Key: JBIDE-21711 > URL: https://issues.jboss.org/browse/JBIDE-21711 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.3.1.CR1 > > > When doing hot code reload in an OpenShift deployed EAP server, changing a method signature will make the debugger complain with > !http://content.screencast.com/users/fbricon/folders/Jing/media/623c96cc-ae62-441b-b498-a39d9cf9b563/00000322.png|width=650! > Triggering a full publish on the module is not sufficient. > We need to at least have a way to trigger a module restart -- 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 reassigned JBIDE-21904: ---------------------------------------- Assignee: Andre Dietisheim (was: Viacheslav Kabanovich) > 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] (JBIDE-21904) Pod deployment path is not reflecting selected service

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21904?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21904: ----------------------------------------------- This must be included in JBIDE-21830 which is in progress now. [~adietish], please check that pull request to JBIDE-21830 fixes this issue as well. > 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: Viacheslav Kabanovich > 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] (JBIDE-21912) Hibernate 5.1 Support

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21912?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-21912. ------------------------------------ verified on nightly. > Hibernate 5.1 Support > --------------------- > > Key: JBIDE-21912 > URL: https://issues.jboss.org/browse/JBIDE-21912 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 4.3.1.Beta2 > Reporter: Koen Aers > Assignee: Koen Aers > Labels: new_and_noteworthy > Fix For: 4.3.1.CR1 > > > With the release of Hibernate Core 5.1, we need to integrate a runtime containing these libraries into JBoss Tools. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21912) Hibernate 5.1 Support

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21912?page=com.atlassian.jira.plugi... ] Rastislav Wagner resolved JBIDE-21912. -------------------------------------- Resolution: Done > Hibernate 5.1 Support > --------------------- > > Key: JBIDE-21912 > URL: https://issues.jboss.org/browse/JBIDE-21912 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 4.3.1.Beta2 > Reporter: Koen Aers > Assignee: Koen Aers > Labels: new_and_noteworthy > Fix For: 4.3.1.CR1 > > > With the release of Hibernate Core 5.1, we need to integrate a runtime containing these libraries into JBoss Tools. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21735) Hibernate 5.1 Support

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21735?page=com.atlassian.jira.plugi... ] Rastislav Wagner updated JBIDE-21735: ------------------------------------- Fix Version/s: (was: 4.3.1.CR1) > Hibernate 5.1 Support > --------------------- > > Key: JBIDE-21735 > URL: https://issues.jboss.org/browse/JBIDE-21735 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 4.3.1.Beta2 > Reporter: Koen Aers > Assignee: Koen Aers > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha1 > > > With the release of Hibernate Core 5.1, we need to integrate a runtime containing these libraries into JBoss Tools. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21912) Hibernate 5.1 Support

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBIDE-21912: ---------------------------------------- Summary: Hibernate 5.1 Support Key: JBIDE-21912 URL: https://issues.jboss.org/browse/JBIDE-21912 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: hibernate Affects Versions: 4.3.1.Beta2 Reporter: Koen Aers Assignee: Koen Aers Fix For: 4.3.1.CR1, 4.4.0.Alpha1 With the release of Hibernate Core 5.1, we need to integrate a runtime containing these libraries into JBoss Tools. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21912) Hibernate 5.1 Support

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21912?page=com.atlassian.jira.plugi... ] Rastislav Wagner updated JBIDE-21912: ------------------------------------- Fix Version/s: (was: 4.4.0.Alpha1) > Hibernate 5.1 Support > --------------------- > > Key: JBIDE-21912 > URL: https://issues.jboss.org/browse/JBIDE-21912 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 4.3.1.Beta2 > Reporter: Koen Aers > Assignee: Koen Aers > Labels: new_and_noteworthy > Fix For: 4.3.1.CR1 > > > With the release of Hibernate Core 5.1, we need to integrate a runtime containing these libraries into JBoss Tools. -- 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: Viacheslav Kabanovich > 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: Viacheslav Kabanovich > 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