April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3830) Vagrant detection does not work if its installation path has spaces

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3830?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3830: ------------------------------------- Vagrant will work fine, the problem is only with .vagrant.d file location has spaces. > Vagrant detection does not work if its installation path has spaces > ------------------------------------------------------------------- > > Key: JBDS-3830 > URL: https://issues.jboss.org/browse/JBDS-3830 > 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 > Fix For: 10.0.0.Alpha1 > > > I have installed Vagrant 1.8.1 into c:\Hashi Corp\Vagrant\ > On the confirmation page it says there is an existing vagrant installation, but it provides no info as to what version or where it is located. > Clicking install -> vagrant starts downloading, the existing installation is not used. Then the installation fails because a newer version is already installed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3748) Installer - We need to define/document the minimum hardware requirements for the installer (and packages installed by the installer)

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3748?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3748: ------------------------------------- [~hardy.ferentschik] that is middle point between smallest and biggest recommended size for windows paging file. But I agree it is a bit to high, because VM maximum memory is limited, so this paging file will probably never go that far. > Installer - We need to define/document the minimum hardware requirements for the installer (and packages installed by the installer) > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-3748 > URL: https://issues.jboss.org/browse/JBDS-3748 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: documentation, installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Misha Ali > Labels: havoc > Fix For: 9.1.0.GA > > > The latest information that I can find for JBDS is: > https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > This is not adequate for the CDK, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3796) Installer: change link to Cygwin installer back to https

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3796?page=com.atlassian.jira.plugin.... ] Alexey Kazakov resolved JBDS-3796. ---------------------------------- Resolution: Done > Installer: change link to Cygwin installer back to https > -------------------------------------------------------- > > Key: JBDS-3796 > URL: https://issues.jboss.org/browse/JBDS-3796 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Reporter: Pavol Pitonak > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.GA > > > The build was failing on *check-requirements* because of an issue with cygwin.com certificate. I changed URL in requirements.json from https to http. It should be changed back to *https* as soon as possible. > How to reproduce: > {code} > $ wget https://cygwin.com/setup-x86_64.exe > --2016-04-13 09:14:28-- https://cygwin.com/setup-x86_64.exe > Resolving cygwin.com (cygwin.com)... 209.132.180.131 > Connecting to cygwin.com (cygwin.com)|209.132.180.131|:443... connected. > ERROR: cannot verify cygwin.com's certificate, issued by ‘CN=DigiCert SHA2 High Assurance Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US’: > Unable to locally verify the issuer's authority. > To connect to cygwin.com insecurely, use `--no-check-certificate'. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3796) Installer: change link to Cygwin installer back to https

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3796?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3796: -------------------------------------- reverted by https://github.com/redhat-developer-tooling/developer-platform-install/co... > Installer: change link to Cygwin installer back to https > -------------------------------------------------------- > > Key: JBDS-3796 > URL: https://issues.jboss.org/browse/JBDS-3796 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Reporter: Pavol Pitonak > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.GA > > > The build was failing on *check-requirements* because of an issue with cygwin.com certificate. I changed URL in requirements.json from https to http. It should be changed back to *https* as soon as possible. > How to reproduce: > {code} > $ wget https://cygwin.com/setup-x86_64.exe > --2016-04-13 09:14:28-- https://cygwin.com/setup-x86_64.exe > Resolving cygwin.com (cygwin.com)... 209.132.180.131 > Connecting to cygwin.com (cygwin.com)|209.132.180.131|:443... connected. > ERROR: cannot verify cygwin.com's certificate, issued by ‘CN=DigiCert SHA2 High Assurance Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US’: > Unable to locally verify the issuer's authority. > To connect to cygwin.com insecurely, use `--no-check-certificate'. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3831) A little typo in detection info

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3831?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3831: -------------------------------------- Marking as a candidate for respin only because it's super trivial. > A little typo in detection info > ------------------------------- > > Key: JBDS-3831 > URL: https://issues.jboss.org/browse/JBDS-3831 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Joshua Wilson > Priority: Trivial > Labels: havoc, respin-a, ui > Fix For: 9.1.0.GA > > > When a different version than recommended is found, it says "Newer/Older that recommended!" instead of "than recommended!" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3832) Investigate if one can find if a pre-installed virtualbox also contains network drivers

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3832?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3832: --------------------------------- Fix Version/s: 10.0.0.Alpha1 > Investigate if one can find if a pre-installed virtualbox also contains network drivers > --------------------------------------------------------------------------------------- > > Key: JBDS-3832 > URL: https://issues.jboss.org/browse/JBDS-3832 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha1 > > > In order to start CDK we need Virtualbox with its networking support installed. Since the vbox installer allows the users to only install the bare VM, we should find a way to tell if the vbox network drivers have been installed in the detected installation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3831) A little typo in detection info

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3831?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3831: --------------------------------- Labels: havoc respin-a ui (was: havoc ui) > A little typo in detection info > ------------------------------- > > Key: JBDS-3831 > URL: https://issues.jboss.org/browse/JBDS-3831 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Joshua Wilson > Priority: Trivial > Labels: havoc, respin-a, ui > Fix For: 9.1.0.GA > > > When a different version than recommended is found, it says "Newer/Older that recommended!" instead of "than recommended!" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3831) A little typo in detection info

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3831?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3831: --------------------------------- Fix Version/s: 9.1.0.GA > A little typo in detection info > ------------------------------- > > Key: JBDS-3831 > URL: https://issues.jboss.org/browse/JBDS-3831 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Joshua Wilson > Priority: Trivial > Labels: havoc, ui > Fix For: 9.1.0.GA > > > When a different version than recommended is found, it says "Newer/Older that recommended!" instead of "than recommended!" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3820) Run the msi installers with suppressed UI

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3820?page=com.atlassian.jira.plugin.... ] Denis Golovin edited comment on JBDS-3820 at 4/15/16 1:05 PM: -------------------------------------------------------------- Good idea :) but we need to check privilege level and if not lifted run with limited UI. was (Author: dgolovin): Good idea:) we can do that for vagrant and oracle PR is here https://github.com/redhat-developer-tooling/developer-platform-install/pu.... > Run the msi installers with suppressed UI > ----------------------------------------- > > Key: JBDS-3820 > URL: https://issues.jboss.org/browse/JBDS-3820 > 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: 10.0.0.Alpha1 > > > If I remember correctly, we've been running the msi installers with reduced UI (/qb) because suppressing the UI required administrative privileges. > Since the 7zipped installer needs those privileges to start, we could switch to using suppressed UI (/qn), could we not? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3830) Vagrant detection does not work if its installation path has spaces

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3830?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3830: -------------------------------------- btw, vargant won't work if installed in some folder with spaces. > Vagrant detection does not work if its installation path has spaces > ------------------------------------------------------------------- > > Key: JBDS-3830 > URL: https://issues.jboss.org/browse/JBDS-3830 > 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 > Fix For: 10.0.0.Alpha1 > > > I have installed Vagrant 1.8.1 into c:\Hashi Corp\Vagrant\ > On the confirmation page it says there is an existing vagrant installation, but it provides no info as to what version or where it is located. > Clicking install -> vagrant starts downloading, the existing installation is not used. Then the installation fails because a newer version is already installed. -- 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