March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3712) Define minimum system requirements for the all-in-1 installer

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3712?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3712: -------------------------------- > Define minimum system requirements for the all-in-1 installer > ------------------------------------------------------------- > > Key: JBDS-3712 > URL: https://issues.jboss.org/browse/JBDS-3712 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Srna > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.CR1 > > > We need to have minimum system requirements defined for the all-in-1 installer. > What is the minimum memory required etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3712) Define minimum system requirements for the all-in-1 installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3712?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3712: ----------------------------------- Target Release: 9.1.0.GA Assignee: Denis Golovin > Define minimum system requirements for the all-in-1 installer > ------------------------------------------------------------- > > Key: JBDS-3712 > URL: https://issues.jboss.org/browse/JBDS-3712 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Srna > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.CR1 > > > We need to have minimum system requirements defined for the all-in-1 installer. > What is the minimum memory required etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3706) Installer: Upgrade patternfly to latest stable version

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3706?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3706: -------------------------------- Target Release: 9.1.0.GA Affects Version/s: 9.1.0.CR1 > Installer: Upgrade patternfly to latest stable version > ------------------------------------------------------ > > Key: JBDS-3706 > URL: https://issues.jboss.org/browse/JBDS-3706 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Pitonak > Assignee: Joshua Wilson > Labels: havoc > Fix For: 9.1.0.CR1 > > > Installer uses PatterFly 2.6.0, it should be upgraded to the latest stable release (3.3.1 on March 23). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21996) Order of project in New OS3 Server Adapter wizard could be better

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21996?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21996: ---------------------------------- Labels: openshift_v3 server_adapter_wizard (was: ) > Order of project in New OS3 Server Adapter wizard could be better > ----------------------------------------------------------------- > > Key: JBIDE-21996 > URL: https://issues.jboss.org/browse/JBIDE-21996 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Labels: openshift_v3, server_adapter_wizard > > With latest changes to New OS3 Server Adapter wizard the current order of projects, listed on wizard page where service selection is done, is a bit strange. At first there are alphanumeric ordered projects with no services and therefore they are not useful for creation of a new OS3 Server Adapter and then there are projects with any service ordered in alphanumberic order. It results in following. > Assume project aproject with no services, bproject with a service, c project with no services, d project with a service. Order on the wizard page is following: > a > c > b > d > I think we are safe not to list projects with no services there or otherwise we should keep alphanumeric order regardless existence of a service under a project. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21996) Order of project in New OS3 Server Adapter wizard could be better

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21996: ------------------------------------- Summary: Order of project in New OS3 Server Adapter wizard could be better Key: JBIDE-21996 URL: https://issues.jboss.org/browse/JBIDE-21996 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.3.1.Beta1 Reporter: Marián Labuda With latest changes to New OS3 Server Adapter wizard the current order of projects, listed on wizard page where service selection is done, is a bit strange. At first there are alphanumeric ordered projects with no services and therefore they are not useful for creation of a new OS3 Server Adapter and then there are projects with any service ordered in alphanumberic order. It results in following. Assume project aproject with no services, bproject with a service, c project with no services, d project with a service. Order on the wizard page is following: a c b d I think we are safe not to list projects with no services there or otherwise we should keep alphanumeric order regardless existence of a service under a project. -- 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 Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21904?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21904. --------------------------------- Closed as out of dated. > 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-21995) Hostname is set to localhost when prompt for route is checked

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21995?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21995: ---------------------------------- Labels: openshift_v3 server_adapter (was: openshift_v3) > Hostname is set to localhost when prompt for route is checked > ------------------------------------------------------------- > > Key: JBIDE-21995 > URL: https://issues.jboss.org/browse/JBIDE-21995 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3, server_adapter > > Hostname in Server Editor for an OpenShift 3 application is set to localhost if checkbox "Prompt for route when multiple routes available to show in browser" is checked. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21995) Hostname is set to localhost when prompt for route is checked

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21995: ------------------------------------- Summary: Hostname is set to localhost when prompt for route is checked Key: JBIDE-21995 URL: https://issues.jboss.org/browse/JBIDE-21995 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Marián Labuda Hostname in Server Editor for an OpenShift 3 application is set to localhost if checkbox "Prompt for route when multiple routes available to show in browser" is checked. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21995) Hostname is set to localhost when prompt for route is checked

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21995?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21995: ---------------------------------- Labels: openshift_v3 (was: ) > Hostname is set to localhost when prompt for route is checked > ------------------------------------------------------------- > > Key: JBIDE-21995 > URL: https://issues.jboss.org/browse/JBIDE-21995 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3, server_adapter > > Hostname in Server Editor for an OpenShift 3 application is set to localhost if checkbox "Prompt for route when multiple routes available to show in browser" is checked. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21830) Server Adapter wizard: route selected by default is wrong

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21830?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21830. --------------------------------- Verified in JBDS 9.1.0.CR1. > Server Adapter wizard: route selected by default is wrong > --------------------------------------------------------- > > Key: JBIDE-21830 > URL: https://issues.jboss.org/browse/JBIDE-21830 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.3.1.CR1 > > Attachments: JBoss_-_nodejs-mongodb-example_at_OpenShift_3__console_engint_openshift_com__-_Eclipse_-__Users_max_Documents_workspace-ec2016.png, wrong-default-route.png > > -- 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