March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3692) Decouple what to download from browser/main.js

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3692?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3692: ------------------------------------- After some refactoring and bug fixes I've merged PR with all files that required to download configured in one file requirements.json. > Decouple what to download from browser/main.js > ---------------------------------------------- > > Key: JBDS-3692 > URL: https://issues.jboss.org/browse/JBDS-3692 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Denis Golovin > Labels: havoc > Fix For: 9.1.0.CR1 > > > Current implementation hardcode links to download inside [browser/main.js|https://github.com/redhat-developer-tooling/developer-pla...]. > This should be moved out to configuration file in json format so it can be easily changed inside installer or even downloaded from external link. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3692) Decouple what to download from browser/main.js

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3692?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3692: ----------------------------------- Assignee: Nick Boldt > Decouple what to download from browser/main.js > ---------------------------------------------- > > Key: JBDS-3692 > URL: https://issues.jboss.org/browse/JBDS-3692 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Denis Golovin > Assignee: Nick Boldt > Labels: havoc > Fix For: 9.1.0.CR1 > > > Current implementation hardcode links to download inside [browser/main.js|https://github.com/redhat-developer-tooling/developer-pla...]. > This should be moved out to configuration file in json format so it can be easily changed inside installer or even downloaded from external link. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3700) Red Hat Central displays headlines from October 2015

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3700?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3700: ------------------------------------------- says something that noone noticed this before now ;/ turns out tiny-rss needs to get its feeds manually updated: https://halfelf.org/2012/tiny-tiny-rss/ looking to see if I can enable it on tiny-man. > Red Hat Central displays headlines from October 2015 > ---------------------------------------------------- > > Key: JBDS-3700 > URL: https://issues.jboss.org/browse/JBDS-3700 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 9.1.0.CR1 > Environment: Version: 9.1.0.CR1 > Build id: CR1-v20160314-1117-B409 > Build date: 20160314-1117 > Reporter: Len DiMaggio > Assignee: Max Rydahl Andersen > > See attached screenshot - can central refer to more current headlines? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21923) Enhance import of OpenShift applications

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21923?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-21923 at 3/22/16 1:45 AM: ------------------------------------------------------------------------ Import application wizard now works in the context of a selected project. If it is started from a service (deployment) or a build config it finds the project and may narrow the choice of build configs. But in the past, wizard could be started from connection and show the tree of projects and build configs to select any available build config from any project. This functionality may be restored: !ImportApplication.png! I attach a minimum patch that allows to see this wizard starting from connection, though bugs are possible. [~fbricon], could you please try it? was (Author: scabanovich): Import application wizard now works in the context of a selected project. If it is started from a service (deployment) or a build config it finds the project and may narrow the choice of build configs. But in the past, wizard could be started from connection and show the tree of projects and build configs to select any available build config from any project. This functionality may be restored: !ImportApplication.png! > Enhance import of OpenShift applications > ---------------------------------------- > > Key: JBIDE-21923 > URL: https://issues.jboss.org/browse/JBIDE-21923 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Minor > Fix For: 4.4.x > > Attachments: ImportApplication.png, jbide-21923.patch > > > In JBIDE-21645 context menu item to import an application was removed from context menu of an OpenShift 3 connection. We should add context menu item back and fix it to let user choose desired build config to import. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21923) Enhance import of OpenShift applications

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21923?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-21923: ------------------------------------------ Attachment: jbide-21923.patch > Enhance import of OpenShift applications > ---------------------------------------- > > Key: JBIDE-21923 > URL: https://issues.jboss.org/browse/JBIDE-21923 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Minor > Fix For: 4.4.x > > Attachments: ImportApplication.png, jbide-21923.patch > > > In JBIDE-21645 context menu item to import an application was removed from context menu of an OpenShift 3 connection. We should add context menu item back and fix it to let user choose desired build config to import. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21923) Enhance import of OpenShift applications

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21923?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-21923 at 3/22/16 1:30 AM: ------------------------------------------------------------------------ Import application wizard now works in the context of a selected project. If it is started from a service (deployment) or a build config it finds the project and may narrow the choice of build configs. But in the past, wizard could be started from connection and show the tree of projects and build configs to select any available build config from any project. This functionality may be restored: !ImportApplication.png! was (Author: scabanovich): Import application wizard now works in the context of a selected project. If it is started from a service (deployment) or a build config it finds the project and may narrow the choice of build configs. But in the past, wizard could be started from connection and show the tree of projects and build configs to select any available build config from any project. This functionality may be restored. > Enhance import of OpenShift applications > ---------------------------------------- > > Key: JBIDE-21923 > URL: https://issues.jboss.org/browse/JBIDE-21923 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Minor > Fix For: 4.4.x > > Attachments: ImportApplication.png > > > In JBIDE-21645 context menu item to import an application was removed from context menu of an OpenShift 3 connection. We should add context menu item back and fix it to let user choose desired build config to import. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21923) Enhance import of OpenShift applications

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21923?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-21923: ------------------------------------------ Attachment: ImportApplication.png > Enhance import of OpenShift applications > ---------------------------------------- > > Key: JBIDE-21923 > URL: https://issues.jboss.org/browse/JBIDE-21923 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Minor > Fix For: 4.4.x > > Attachments: ImportApplication.png > > > In JBIDE-21645 context menu item to import an application was removed from context menu of an OpenShift 3 connection. We should add context menu item back and fix it to let user choose desired build config to import. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3661) Remove VAGRANT_DETECTED_OS from env variables in CDK launch config on Windows

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3661?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-3661. --------------------------------- Resolution: Rejected reverted in master and 4.3.x branches. > Remove VAGRANT_DETECTED_OS from env variables in CDK launch config on Windows > ----------------------------------------------------------------------------- > > Key: JBDS-3661 > URL: https://issues.jboss.org/browse/JBDS-3661 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, server > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: havoc > > With mingw based ssh/rsync this env varibale is not required. > It is also set in windows user env variables, so there is no reason to duplicate that anyway. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-714) JBDS 9.1 GA: Win Installation - changing JDK with installed JBDS fails

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-714?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-714: ------------------------------- Description: Ideally, if the user has an existing JBDS installation in their Program Files folder in Win and the installer is used to install the JDK, the installation fails when the installer tries to alter the jbdevstudio.ini file to point to the new JDK. Windows does not allow a protected folder's contents to be modified without admin rights. The issue is being discussed and may require documentation. Source: https://issues.jboss.org/browse/JBDS-3695 > JBDS 9.1 GA: Win Installation - changing JDK with installed JBDS fails > ---------------------------------------------------------------------- > > Key: TOOLSDOC-714 > URL: https://issues.jboss.org/browse/TOOLSDOC-714 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 9.1 GA > Reporter: Misha Ali > Assignee: Misha Ali > Labels: Windows > > Ideally, if the user has an existing JBDS installation in their Program Files folder in Win and the installer is used to install the JDK, the installation fails when the installer tries to alter the jbdevstudio.ini file to point to the new JDK. Windows does not allow a protected folder's contents to be modified without admin rights. The issue is being discussed and may require documentation. > Source: https://issues.jboss.org/browse/JBDS-3695 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3695) Using existing JBDS with downloaded/installed JDK fails if JBDS is in Program Files folder

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3695?page=com.atlassian.jira.plugin.... ] Misha Ali commented on JBDS-3695: --------------------------------- Thanks, Len. Tracking for potential docs impact after resolution here: https://issues.jboss.org/browse/TOOLSDOC-714 > Using existing JBDS with downloaded/installed JDK fails if JBDS is in Program Files folder > ------------------------------------------------------------------------------------------ > > Key: JBDS-3695 > URL: https://issues.jboss.org/browse/JBDS-3695 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > > So if the user selects an existing JBDS installation from their Program Files folder and lets us install JDK, the installation will fail when the installer tries to change jbdevstudio.ini to point to the JDK we installed. > The problem once again is in windows magic, it does not allow to modify files in a protected folder without administrative rights. -- 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