August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4026) Bundled binaries sha256 is not verified after download in online installer

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-4026?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-4026: ----------------------------- > Bundled binaries sha256 is not verified after download in online installer > -------------------------------------------------------------------------- > > Key: JBDS-4026 > URL: https://issues.jboss.org/browse/JBDS-4026 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Denis Golovin > > sha256 checksum verification was not implemented for 'bundled' binaries, that affects: > # OpenJDK > # DevStudio > # CDK > # Virtualbox.box -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4026) Bundled binaries sha256 is not verified after download in online installer

by Denis Golovin (JIRA)

Denis Golovin created JBDS-4026: ----------------------------------- Summary: Bundled binaries sha256 is not verified after download in online installer Key: JBDS-4026 URL: https://issues.jboss.org/browse/JBDS-4026 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 10.1.0.GA Reporter: Denis Golovin sha256 checksum verification was not implemented for 'bundled' binaries, that affects: # OpenJDK # DevStudio # CDK # Virtualbox.box -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4026) Bundled binaries sha256 is not verified after download in online installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4026?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4026: -------------------------------- > Bundled binaries sha256 is not verified after download in online installer > -------------------------------------------------------------------------- > > Key: JBDS-4026 > URL: https://issues.jboss.org/browse/JBDS-4026 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Denis Golovin > > sha256 checksum verification was not implemented for 'bundled' binaries, that affects: > # OpenJDK > # DevStudio > # CDK > # Virtualbox.box -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4026) Bundled binaries sha256 is not verified after download in online installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4026?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4026: -------------------------------- > Bundled binaries sha256 is not verified after download in online installer > -------------------------------------------------------------------------- > > Key: JBDS-4026 > URL: https://issues.jboss.org/browse/JBDS-4026 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Denis Golovin > > sha256 checksum verification was not implemented for 'bundled' binaries, that affects: > # OpenJDK > # DevStudio > # CDK > # Virtualbox.box -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3627: -------------------------------- Sprint: (was: devex #119 August 2016) > Installer needs to help move past lack of t/c signing > ----------------------------------------------------- > > Key: JBDS-3627 > URL: https://issues.jboss.org/browse/JBDS-3627 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Joshua Wilson > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.1.0.GA > > Attachments: Installer-not-signed-tc.PNG > > > DevSuite installer uses "REST services in JBoss Download Manager" explained here https://mojo.redhat.com/docs/DOC-940689. > DevSuite Intsaller follows the explanation for tc-accepted entry point [code is here|https://github.com/redhat-developer-tooling/developer-platform-insta...]. It uses file from previous CDK release (published in cdn and available through download manager) to do verification: > 1. that provided credentials are valid; > 2. that required T&C's are signed. > There are two major use cases for developers installing DevSuite using Installer: > 1. Direct download - when developer sign in to developers.redhat.com and download installer himeslf; > 2. Shared installer - when someone share installer with developers without account. > There two kind of users involved in those scenarios above: > 1. New users that must go through registration process; > 2. Registered users. > *Direct download* > For new ones registration process is really simple now. After creating RHD account and downloading installer there is no additional steps to get through installation. > For already registered users there could be problems related to T&C's and authentication reported here https://issues.jboss.org/browse/RHDENG-579. > So far there are two kind of problems: > 1. Users can login and download DevSuite installer, but cannot use the same credentials to install; > 2. Users that can login in to developers.redhat.com and get request to sign additional T&C's but credentials for the same user in DevSuite Installer reported as invalid when REST tc-accepted entry point is used > *Shared Download* > In this scenario new users without account can press Register link, then go through registration process in browser return back to installer and use new account credentials for installation. > Registered users could need to sign additional T&C's if missing and would be good to show external link to do so. Current entry point tc-accepted does not provide any hints where missing T&C's could be signed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3931) Installed OC binary is not used by default if user has another OC already on system path

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3931?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3931: -------------------------------- Sprint: (was: devex #119 August 2016) > Installed OC binary is not used by default if user has another OC already on system path > ---------------------------------------------------------------------------------------- > > Key: JBDS-3931 > URL: https://issues.jboss.org/browse/JBDS-3931 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 10.1.0.GA > > > I tried to install everything on a machine where an existing OC binary was already on path. The newly installed devstudio then used it by default instead of the bundled one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3822) Disable the annoying "This program might not have installed correctly" on cancelation

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3822?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3822: -------------------------------- Sprint: (was: devex #119 August 2016) > Disable the annoying "This program might not have installed correctly" on cancelation > ------------------------------------------------------------------------------------- > > Key: JBDS-3822 > URL: https://issues.jboss.org/browse/JBDS-3822 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.1.0.GA > > Attachments: devsuite.manifest > > > Upon closing/cancelling the installer before going through the entire installation process, Windows will open a dialog saying "This program might not have installed correctly" and the user has to somehow confirm it. > This should be avoided by providing an application manifest that indicates support for certain Windows versions. > Docs here: > https://msdn.microsoft.com/en-us/library/dd371711%28VS.85%29.aspx -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3981) Build a new feature that omits features available from RPM install

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-3981?page=com.atlassian.jira.plugin.... ] Pavol Srna commented on JBDS-3981: ---------------------------------- Hi [~nickboldt], me and [~vkadlcik] were wondering Today about where is the spec file. Can you please point us to the right place. Thanks! > Build a new feature that omits features available from RPM install > ------------------------------------------------------------------ > > Key: JBDS-3981 > URL: https://issues.jboss.org/browse/JBDS-3981 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 10.1.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.1.0.GA > > Attachments: .log, feature_dupe_check.sh, IUs-removed-from-rh-eclipse46-devstudio.rpm.txt, IUs-removed-from-rh-eclipse46-devstudio.rpm_more.txt, rh-eclipse46-devstudio.provides.list.01, rh-eclipse46-devstudio.provides.list.02, simpler_install_foorprint_rh-eclipse46-devstudio.rpm.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_2.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_3.png > > > What we DO need is a feature with fewer dependencies than com.jboss.devstudio.core.feature (eg., which omits pde, emf, xsd, egit...) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23029) Integration tests: Tests should be able to run individually

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23029?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-23029: ---------------------------------------- Story Points: 32 Assignee: Andre Dietisheim > Integration tests: Tests should be able to run individually > ----------------------------------------------------------- > > Key: JBIDE-23029 > URL: https://issues.jboss.org/browse/JBIDE-23029 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration_tests > Fix For: 4.4.x > > > We should be able to run the bot tests individually. Currently you cant because the suite is setting up requirements (ex. ScalingTest requires a connection. The connection though is set up in the CreateNewConnectionTest. You thus cant run ScalingTest only, you need to copy the suite, comment all the tests that you dont need). > This is even more true since running the whole suite is a lengthy task. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22653) Scale Pod: should get warned when scaling to 0

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22653?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22653 at 8/31/16 5:12 AM: ------------------------------------------------------------------- This was verified and merged into master by [~jeffmaury] and [~rhopp]. Thx! was (Author: adietish): This was verified and merged into master by @Jeff Maury and [~rhopp]. Thx! > Scale Pod: should get warned when scaling to 0 > ---------------------------------------------- > > Key: JBIDE-22653 > URL: https://issues.jboss.org/browse/JBIDE-22653 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Labels: openshift_v3, scaling_pods_wizard > Fix For: 4.4.1.Final > > > The scale to... menu lets you scale to any number of replicas, but you can't go down to 0. > The webconsoles allows it, albeit with a big warning: "Are you sure you want to scale deploymentname to 0 replicas? This will stop all pods for the deployment." > My take is we should have the same behavior in eclipse -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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 August 2016