[jbosstools-issues] [JBoss JIRA] (JBDS-3213) Installer hangs at P2 director when command prompt is disabled

Nick Boldt (JIRA) issues at jboss.org
Mon Sep 10 09:26:00 EDT 2018


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

Nick Boldt commented on JBDS-3213:
----------------------------------

If you can't use the installer because your Windows install is locked down, and can't unlock the permissions, you can install Eclipse yourself (download the zip, unpack it), then install the devstudio features into that via its update site or via Eclipse Marketplace.

https://access.redhat.com/documentation/en-us/red_hat_developer_studio/12.0/html/installation_guide/assembly_installing-devstudio-in-eclipse#proc_installing-devstudio-in-eclipse-when-online

Or, you could try launching a Windows Powershell (Admin) console, then run this:

{code}java c:\path\to\where\you\downloaded\devstudio-installer.jar{code}

https://access.redhat.com/documentation/en-us/red_hat_developer_studio/12.0/html/installation_guide/proc_installing-devstudio-stand-alone-using-the-installer

> Installer hangs at P2 director when command prompt is disabled
> --------------------------------------------------------------
>
>                 Key: JBDS-3213
>                 URL: https://issues.jboss.org/browse/JBDS-3213
>             Project: Red Hat JBoss Developer Studio (devstudio)
>          Issue Type: Bug
>          Components: installer
>    Affects Versions: 8.0.0.GA
>         Environment: Windows 7 Ultimate with group policy "Prevent access to the command prompt" enabled
>            Reporter: Richard Hands
>            Assignee: Denis Golovin
>             Fix For: 9.x, 12.9.0.GA
>
>
> Trying to install JBDS 8.0.0.GA in a customer locked down environment, on a windows machine which has the group policy for locking out the cmd prompt enabled causes the installer to hang at the P2 Director stage.  Running with -DTRACE=TRUE shows that it gets to running java -jar ...JBDS.....jar but is trying to use some mechanism which on windows invokes the command prompt, and we end up with, in the console, the message
> The command prompt has been disabled by your administrator.
> Press any key to continue . . .
> but this is hidden when not running in -DTRACE=TRUE mode, and even in trace mode, you can't hit a key as the installer has focus and not the console



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)


More information about the jbosstools-issues mailing list