[jbosstools-issues] [JBoss JIRA] (JBDS-3664) Do we still need/want custom build of vagrant ?

[Denis Golovin (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13179506#comment-13179506 ] 

Denis Golovin commented on JBDS-3664:
-------------------------------------

It is resolved by switching to original vagrant installer (see JBDS-3691). 
Until redirects are done (see JBDS-3663) we are using direct links. 
Links are hardcoded now in [browser/main.js|https://github.com/redhat-developer-tooling/developer-platform-install/blob/master/browser/main.js#L69] unil I figure out how to move them out to config file in json format (see JBDS-3692).
Installer is called with /qb option (basic UI) the same way as virtualbox one. It means all original request for privilege lifting are shown with original publisher 'HashiCorp, Inc.' and MSI installer progress UI is shown.

> Do we still need/want custom build of vagrant ?
> -----------------------------------------------
>
>                 Key: JBDS-3664
>                 URL: https://issues.jboss.org/browse/JBDS-3664
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Task
>          Components: installer
>            Reporter: Max Rydahl Andersen
>            Assignee: Denis Golovin
>            Priority: Blocker
>              Labels: havoc
>             Fix For: 9.1.0.CR1
>
>
> we seem to install use our custom vagrant build.
> Is that still relevant ?
> With that we need to test much more since our build could be different.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)