March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21899) Wrong service is preselected when creating a new OS3 server adapter from context menu of a service

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21899?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-21899. -------------------------------------- Resolution: Done > Wrong service is preselected when creating a new OS3 server adapter from context menu of a service > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-21899 > URL: https://issues.jboss.org/browse/JBIDE-21899 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.3.1.CR1 > > > When I am creating a new OpenShift 3 server adapter from context menu of a service in OpenShift explorer view and I am having several projects and at least 2 same services (names must be equal) in different projects, then in New OS 3 Server Wizard is wrong service. This is happening when I am trying to create a server adapter from context menu of a service which is lower (in order of tree items under an OpenShift 3 connection) then a service with same name. -- 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 Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21830?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21830: ------------------------------------------ merged into jbosstools-4.3.x > 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

[JBoss JIRA] (JBDS-3652) Installer - Replace use of JBDS installer with JBDS product archive - to save time

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3652?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3652: ------------------------------------------- What is the problem here ? Why is it believed that unzipping it will be faster/more correct ? And note, the reason we do use the installer is so we get the exact same behavior and setup as if you use the devstudio installer directly or installed it via p2 into existing eclipse. > Installer - Replace use of JBDS installer with JBDS product archive - to save time > ---------------------------------------------------------------------------------- > > Key: JBDS-3652 > URL: https://issues.jboss.org/browse/JBDS-3652 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc, performance > Fix For: 9.1.0.GA > > > The current installer runs for several minutes when it invokes the JBDS installer - can we replace this a JBDS product archive and some follow-on tasks (such as setting the JDK location)? Thx! -- 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: ------------------------------------------ we do not infer the deployment path in the wizard any more. We just allow the user to tellt the server adapter to automatically determine (infer) the deployment path when publishing. We're are not displaying it in the wizard any more. This is highly beneficial to the startup time reported in JBIDE-21858. Thus this issue went obsolete. > 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-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 resolved JBIDE-21904. -------------------------------------- Resolution: Out of Date > 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] (JBDS-3669) Inject version, timestamp and Jenkins build number into installer to show in installer window

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3669?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3669: ---------------------------------- OK, so managed to make this work: https://github.com/redhat-developer-tooling/developer-platform-install/pu... in that we can pass in some value of --version to the gulp process to name the .exe whatever we want (rather than having to call `npm version`). BUT... I can't get the same parameter to flow into browser/pages/account/controller.js such that any value other than the one in package.json appears in account.html 's footer on line 58 as `acctCtrl.pdkVersion`. So this is the best I can do for now. > Inject version, timestamp and Jenkins build number into installer to show in installer window > --------------------------------------------------------------------------------------------- > > Key: JBDS-3669 > URL: https://issues.jboss.org/browse/JBDS-3669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.CR1 > > > Currently this information is not available in installer at execution time, we should create json or js file with this info before executing the build, include it in installer and use during installation to get required data. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3710) use brackets logo for Developer Platform installer

by Joshua Wilson (JIRA)

[ https://issues.jboss.org/browse/JBDS-3710?page=com.atlassian.jira.plugin.... ] Joshua Wilson commented on JBDS-3710: ------------------------------------- Has it been decided what the logo for the UI will look like or is this all for the icon? > use brackets logo for Developer Platform installer > -------------------------------------------------- > > Key: JBDS-3710 > URL: https://issues.jboss.org/browse/JBDS-3710 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Max Rydahl Andersen > Assignee: Joshua Wilson > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > Attachments: RedHatDeveloperStudio_Logo_Installer.ico > > > Based on feedback from [~pmuir], [~tmancini] and [~crobson] we'll go for using the brackets logo for the big Developer Platform installers (56M stub and 1.6G bundled). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3710) use brackets logo for Developer Platform installer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3710?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3710: ----------------------------- Description: Based on feedback from [~pmuir], [~tmancini] and [~crobson] we'll go for using the brackets logo for the big Developer Platform installers (50M stub and 1.6G bundled). was: based on feedback from [~pmuir], [~tmancini] and [~crobson] we'll go for using the brackets logo for the big installer. > use brackets logo for Developer Platform installer > -------------------------------------------------- > > Key: JBDS-3710 > URL: https://issues.jboss.org/browse/JBDS-3710 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Max Rydahl Andersen > Assignee: Joshua Wilson > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > Attachments: RedHatDeveloperStudio_Logo_Installer.ico > > > Based on feedback from [~pmuir], [~tmancini] and [~crobson] we'll go for using the brackets logo for the big Developer Platform installers (50M stub and 1.6G bundled). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3710) use brackets logo for Developer Platform installer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3710?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3710: ----------------------------- Description: Based on feedback from [~pmuir], [~tmancini] and [~crobson] we'll go for using the brackets logo for the big Developer Platform installers (56M stub and 1.6G bundled). was: Based on feedback from [~pmuir], [~tmancini] and [~crobson] we'll go for using the brackets logo for the big Developer Platform installers (50M stub and 1.6G bundled). > use brackets logo for Developer Platform installer > -------------------------------------------------- > > Key: JBDS-3710 > URL: https://issues.jboss.org/browse/JBDS-3710 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Max Rydahl Andersen > Assignee: Joshua Wilson > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > Attachments: RedHatDeveloperStudio_Logo_Installer.ico > > > Based on feedback from [~pmuir], [~tmancini] and [~crobson] we'll go for using the brackets logo for the big Developer Platform installers (56M stub and 1.6G bundled). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3710) use brackets logo for big installer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3710?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3710: ---------------------------------- Also, are we doing this new "[] Red Hat Developer Platform" logo on a WHITE background, consistent w/ the way the installer looks today? Or are we switching it to a BLACK background, consistent with the new branding in JBDS-3605 ? (I'd assume WHITE background.) > use brackets logo for big installer > ----------------------------------- > > Key: JBDS-3710 > URL: https://issues.jboss.org/browse/JBDS-3710 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Max Rydahl Andersen > Assignee: Joshua Wilson > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > Attachments: RedHatDeveloperStudio_Logo_Installer.ico > > > based on feedback from [~pmuir], [~tmancini] and [~crobson] we'll go for using the brackets logo for the big installer. -- 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