June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4402) Devsuite 1.4 Windows re-runs installed component checks on expose events

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4402?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4402: ----------------------------- Fix Version/s: 11.0.0.AM2 (was: 11.0.0.AM1) Slip to AM2 > Devsuite 1.4 Windows re-runs installed component checks on expose events > ------------------------------------------------------------------------ > > Key: JBDS-4402 > URL: https://issues.jboss.org/browse/JBDS-4402 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Environment: Windows 10 64-bit Pro, DevSuite 1.4 GA installer > Reporter: Robert Terzi > Assignee: Denis Golovin > Labels: ui > Fix For: 11.0.0.AM2 > > > The DevSuite Windows installer re-runs the search for installed components every time there is a window event like restore/bring to front, minimize, etc. Considering how long it can take this can be quite annoying. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4247) Replace 7Zip self extracting executable

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4247?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4247: ----------------------------- Fix Version/s: 11.0.0.AM2 (was: 11.0.0.AM1) Slip to AM2 > Replace 7Zip self extracting executable > --------------------------------------- > > Key: JBDS-4247 > URL: https://issues.jboss.org/browse/JBDS-4247 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.3.0.AM2 > Environment: Windows > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 11.0.0.AM2 > > > Implement simple installer based on [go-bindata:https://github.com/jteeuwen/go-bindata]. > It would do simple thing similar to other self-extracting installers, unpack specific Asset from executable and run it. > In case of windows installer it would speedup installation. because instead of extracting everything for bundle installer as 7Zip does, it would pull only installer first and run it. Then every specific installer selected for installation would first pull data out of installer executable with go-bindata. > This approach would fix several opened issues that should be addressed upstream in 7Zip selexecuatble. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4164) Project Examples don't work behind proxy

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4164?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4164: ----------------------------- Fix Version/s: 11.0.0.AM2 (was: 11.0.0.AM1) Slip to AM2 > Project Examples don't work behind proxy > ---------------------------------------- > > Key: JBDS-4164 > URL: https://issues.jboss.org/browse/JBDS-4164 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: jbpm, project-examples, upstream > Affects Versions: 9.1.0.GA > Reporter: Denis Golovin > Assignee: Dmitrii Bocharov > Fix For: 11.0.0.AM2 > > > Issue is reported on forum (see [forum reference|https://developer.jboss.org/message/964401#964401]). Examples does not work behind proxy with eclipse configured to use proxy in settings. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3965) Add a note on how to launch cdk in last page of devsuite installer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3965?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3965: ----------------------------- Fix Version/s: 11.0.0.AM2 (was: 11.0.0.AM1) Slip to AM2 > Add a note on how to launch cdk in last page of devsuite installer > ------------------------------------------------------------------ > > Key: JBDS-3965 > URL: https://issues.jboss.org/browse/JBDS-3965 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.1.0.AM2 > Reporter: Martin Malina > Assignee: Denis Golovin > Fix For: 11.0.0.AM2 > > > Recently, [~rick_wagner] gave us some feedback on how he tried to use the devsuite installer and then connect to the docker daemon running in cdk. > This is described here: JBIDE-22734 > What happened was that Rick didn't know he was supposed to start CDK from the Servers view. Having some prior knowledge of CDK, he started it from CLI. Then he went to the Docker Explorer view and wanted to connect to cdk's docker daemon. > Normally, the docker connection will be created for you automatically, but that assumes you start the cdk adapter in Servers View. > So here's a proposal: > Perhaps at the end of the devsuite installer, just before devstudio is launched, we could briefly note that to start using CDK, you can start it from the Server view, once devstudio is launched? > Please note that the actual name of the server adapter is probably Container Runtime Environment, but I'm not 100 % sure, this needs to be verified. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3587) Uninstalling features from central is misleading if the feature is required in JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3587?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3587: ----------------------------- Fix Version/s: 11.0.0.AM2 (was: 11.0.0.AM1) Slip to AM2 > Uninstalling features from central is misleading if the feature is required in JBDS > ----------------------------------------------------------------------------------- > > Key: JBDS-3587 > URL: https://issues.jboss.org/browse/JBDS-3587 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 9.1.0.Beta2 > Reporter: Jan Richter > Fix For: 11.0.0.AM2 > > > Since some features are both in default JBDS installation and in central, you can try uninstalling them from central. The uninstall wizard will show a strange cryptic message saying: > {noformat}"#the selected feature# cannot be fully uninstalled because other installed software requires it. The parts that are not required will be uninstalled".{noformat} > That basically means nothing gets uninstalled, but it still requires a restart just for good measure. > The question is - Can it either be more clear that you can't just uninstall those features using central, or just allow it? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4302) Component should declare dependencies in requirements-.json

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4302?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4302: ----------------------------- Fix Version/s: 11.0.0.AM2 (was: 11.0.0.AM1) Slip to AM2 > Component should declare dependencies in requirements-.json > ----------------------------------------------------------- > > Key: JBDS-4302 > URL: https://issues.jboss.org/browse/JBDS-4302 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.4.0.AM2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 11.0.0.AM2 > > > Current implementation for dependencies validation is hardcoded and was originally implemented for static set of components. It should part of components configuration in requirements.json file. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3983) Development Suite Installer should work behind proxy

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3983?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3983: ----------------------------- Fix Version/s: 11.0.0.AM2 (was: 11.0.0.AM1) Slip to AM2 > Development Suite Installer should work behind proxy > ---------------------------------------------------- > > Key: JBDS-3983 > URL: https://issues.jboss.org/browse/JBDS-3983 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: platform-installer > Affects Versions: 10.1.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: release_notes > Fix For: 11.0.0.AM2 > > > DevSuite installer cannot download stack software form external links because it uses nodejs request module without proxy settings: > CDK also requires proxy to be configured to have vagrant up working after installation, which could affect CDK Server Adapter Implementation. > To make DevStudio Installer working behind proxy there should be variable HTTPS_PROXY in user environment which sets up URL to proxy server. URL examples for none auth proxy: > * http(s)://servername.com:3128 > * http(s)://192.168.0.47:3128 > For auth proxy: > * http(s)://username:password@servername.com:3128 > * http(s)://username:password@192.168.0.47:3128 > If you use email as username then replace @ with %40: > * http(s)://username%40server.com:password@servername.com:3128 > * http(s)://username%40server.com:password@192.168.0.47:3128 > Additional details are here https://github.com/request/request#controlling-proxy-behaviour-using-envi.... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4281) Early Access Banner dissappers after restart

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4281?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4281: ----------------------------- Fix Version/s: 11.0.0.AM2 (was: 11.0.0.AM1) Slip to AM2 > Early Access Banner dissappers after restart > -------------------------------------------- > > Key: JBDS-4281 > URL: https://issues.jboss.org/browse/JBDS-4281 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 10.2.0.GA > Reporter: Andrej Podhradsky > Assignee: Fred Bricon > Fix For: 11.0.0.AM2 > > Attachments: ea_banner.png > > > After restarting Devstudio 10.2.0.GA the EA banner dissappears. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4319) Support DevSuite Installer requirements.js loading from remote location

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4319?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4319: ----------------------------- Fix Version/s: 11.0.0.AM2 (was: 11.0.0.AM1) Slip to AM2 > Support DevSuite Installer requirements.js loading from remote location > ----------------------------------------------------------------------- > > Key: JBDS-4319 > URL: https://issues.jboss.org/browse/JBDS-4319 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: platform-installer > Reporter: Denis Golovin > Fix For: 11.0.0.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3756) Have two progress bars download and installation progress

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3756?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3756: ----------------------------- Fix Version/s: 11.0.0.AM2 (was: 11.0.0.AM1) Slip to AM2 > Have two progress bars download and installation progress > --------------------------------------------------------- > > Key: JBDS-3756 > URL: https://issues.jboss.org/browse/JBDS-3756 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Reporter: Pete Muir > Assignee: Denis Golovin > Priority: Minor > Labels: ui > Fix For: 11.0.0.AM2 > > > Most installers have a single progress bar that shows the overall progress, and then text which explains which component is being installed right now. > Update: > After discussion on backlog grooming session it seems reasonable to have two progress bars instead of one. Considering size of downloaded resources and time spend for downloading/installation we might have much longer installation time than now with single progress bar. Instead we can start downloading resources and install them as soon as download is finished. That would let us run installation in sequence and avoid problems with running two MSI installer at the same timed. Also that would save some time and do installation for smaller components while download for big ones is in progress. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

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 June 2017