April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3762) Add logging to configuration page for detection and configured items

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3762?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3762: ----------------------------- > Add logging to configuration page for detection and configured items > -------------------------------------------------------------------- > > Key: JBDS-3762 > URL: https://issues.jboss.org/browse/JBDS-3762 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.1.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: Havoc > Fix For: 9.1.0.GA > > > Log what was detected and selected on configuration page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3762) Add logging to configuration page for detection and configured items

by Denis Golovin (JIRA)

Denis Golovin created JBDS-3762: ----------------------------------- Summary: Add logging to configuration page for detection and configured items Key: JBDS-3762 URL: https://issues.jboss.org/browse/JBDS-3762 Project: Developer Studio (JBoss Developer Studio) Issue Type: Enhancement Components: installer Affects Versions: 9.1.0.GA Reporter: Denis Golovin Assignee: Denis Golovin Log what was detected and selected on configuration page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3762) Add logging to configuration page for detection and configured items

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3762?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3762: -------------------------------- Fix Version/s: 9.1.0.GA > Add logging to configuration page for detection and configured items > -------------------------------------------------------------------- > > Key: JBDS-3762 > URL: https://issues.jboss.org/browse/JBDS-3762 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.1.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: Havoc > Fix For: 9.1.0.GA > > > Log what was detected and selected on configuration page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3757) Add some logging to setup routines

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3757?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3757: ----------------------------- > Add some logging to setup routines > ---------------------------------- > > Key: JBDS-3757 > URL: https://issues.jboss.org/browse/JBDS-3757 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.CR1 > > > We should log events in setup the same way we now do in download and install phases. For example when the install -> setup transition happens, when setup is fired for an already existing item. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3757) Add some logging to setup routines

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3757?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3757: -------------------------------- Status: New (was: New) Target Release: 9.1.0.GA > Add some logging to setup routines > ---------------------------------- > > Key: JBDS-3757 > URL: https://issues.jboss.org/browse/JBDS-3757 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.GA > > > We should log events in setup the same way we now do in download and install phases. For example when the install -> setup transition happens, when setup is fired for an already existing item. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3757) Add some logging to setup routines

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3757?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3757: -------------------------------- Fix Version/s: 9.1.0.CR1 (was: 9.1.0.GA) > Add some logging to setup routines > ---------------------------------- > > Key: JBDS-3757 > URL: https://issues.jboss.org/browse/JBDS-3757 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.CR1 > > > We should log events in setup the same way we now do in download and install phases. For example when the install -> setup transition happens, when setup is fired for an already existing item. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22064) Available selection of route for other project does not contain correct route(s)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22064?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22064: ------------------------------------------ merged into jbosstools-4.3.x > Available selection of route for other project does not contain correct route(s) > -------------------------------------------------------------------------------- > > Key: JBIDE-22064 > URL: https://issues.jboss.org/browse/JBIDE-22064 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > When I have 2 OpenShift projects, first one contains a service and a route and second one contains it too, then in Server Adapter wizard are no available routes to select for a second project. In combo are listed only routes available for first project. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22074) Available selection of route for other project does not contain correct route(s)

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-22074: ---------------------------------------- Summary: Available selection of route for other project does not contain correct route(s) Key: JBIDE-22074 URL: https://issues.jboss.org/browse/JBIDE-22074 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Marián Labuda Assignee: Andre Dietisheim Priority: Critical Fix For: 4.3.1.CR1 When I have 2 OpenShift projects, first one contains a service and a route and second one contains it too, then in Server Adapter wizard are no available routes to select for a second project. In combo are listed only routes available for first project. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22074) Available selection of route for other project does not contain correct route(s)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22074?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22074: ------------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.CR1) > Available selection of route for other project does not contain correct route(s) > -------------------------------------------------------------------------------- > > Key: JBIDE-22074 > URL: https://issues.jboss.org/browse/JBIDE-22074 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha1 > > > When I have 2 OpenShift projects, first one contains a service and a route and second one contains it too, then in Server Adapter wizard are no available routes to select for a second project. In combo are listed only routes available for first project. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3635) Add the ability to detect/select existing dependencies/tools

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3635?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3635: -------------------------------- Description: Generic rules for detection and validation are: 1. We do our best to detect what is installed on user's machine: vagrant, virtualbox, java and do not detect cdk, cygwin, or DevStudio; 2. When version is detected it must be verified against the range of what we believe valid versions; it might be defined as a set or condition. vagrant: minimal and tested version is 1.7.4, all newer releases are good to continue with warning except 1.8.0 which is known to have networking problems; virtualbox: minimal and tested 5.0.8 and all newer releases are good to continue with warning; jvm: minimal and tested is 1.8 and all newer releases are good to continue with warning; 3. For vagrant and virtual box if detected version is out of the range, installer shows error message with explanation and doesn't let go any further until detected version is uninstalled, which should be done manually and then installer should be restarted; If nothing is detected included versions can be installed or installer could be configured to use specific location; 4. For JVM if not supported version is detected, included one can be used or installer could be pointed to right location to use. 5. When location for required software set manually installer try will try detect version and verify it using (2); 6. When version cannot be detected and manually selected location looks like required install, installer should let to proceed with warning. It would be great if the installer allowed the user to use some of the required tools they have already installed. The idea is to detect if the dependencies are already present and let the user decide if they want to use them, or install new ones. Also, it could let the user select the tools themselves if they want to use a different installation than detected, etc. The confirmation page we currently have looks like the place to put all this, since it already displays most of the stuff that is going to get installed. Anyway, I have tried to modify it and squeeze the controls in and this is how the selection turned out (imagine the messages looking a bit smarter): !pdkinstaller.png|thumbnail! [~dgolovin] & [~crobson], what's your opinion on this? was: It would be great if the installer allowed the user to use some of the required tools they have already installed. The idea is to detect if the dependencies are already present and let the user decide if they want to use them, or install new ones. Also, it could let the user select the tools themselves if they want to use a different installation than detected, etc. The confirmation page we currently have looks like the place to put all this, since it already displays most of the stuff that is going to get installed. Anyway, I have tried to modify it and squeeze the controls in and this is how the selection turned out (imagine the messages looking a bit smarter): !pdkinstaller.png|thumbnail! [~dgolovin] & [~crobson], what's your opinion on this? > Add the ability to detect/select existing dependencies/tools > ------------------------------------------------------------ > > Key: JBDS-3635 > URL: https://issues.jboss.org/browse/JBDS-3635 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc, ui > Fix For: 9.1.0.GA > > Attachments: pdkinstaller.png, Technologies 5.pdf > > > Generic rules for detection and validation are: > 1. We do our best to detect what is installed on user's machine: vagrant, virtualbox, java and do not detect cdk, cygwin, or DevStudio; > 2. When version is detected it must be verified against the range of what we believe valid versions; it might be defined as a set or condition. > vagrant: minimal and tested version is 1.7.4, all newer releases are good to continue with warning except 1.8.0 which is known to have networking problems; > virtualbox: minimal and tested 5.0.8 and all newer releases are good to continue with warning; > jvm: minimal and tested is 1.8 and all newer releases are good to continue with warning; > 3. For vagrant and virtual box if detected version is out of the range, installer shows error message with explanation and doesn't let go any further until detected version is uninstalled, which should be done manually and then installer should be restarted; If nothing is detected included versions can be installed or installer could be configured to use specific location; > 4. For JVM if not supported version is detected, included one can be used or installer could be pointed to right location to use. > 5. When location for required software set manually installer try will try detect version and verify it using (2); > 6. When version cannot be detected and manually selected location looks like required install, installer should let to proceed with warning. > It would be great if the installer allowed the user to use some of the required tools they have already installed. > The idea is to detect if the dependencies are already present and let the user decide if they want to use them, or install new ones. Also, it could let the user select the tools themselves if they want to use a different installation than detected, etc. > The confirmation page we currently have looks like the place to put all this, since it already displays most of the stuff that is going to get installed. Anyway, I have tried to modify it and squeeze the controls in and this is how the selection turned out (imagine the messages looking a bit smarter): > !pdkinstaller.png|thumbnail! > [~dgolovin] & [~crobson], what's your opinion on this? -- 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 April 2016